Skip to content

Update discord links to be a valid invite #181

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

joaquinalvarezdev
Copy link

@joaquinalvarezdev joaquinalvarezdev commented Jan 15, 2025

Summary by CodeRabbit

  • Documentation
    • Updated Discord invite links across multiple documentation pages from generic https://discord.gg/evmos to specific https://discord.com/invite/evmos-809048090249134080
    • Ensured consistent Discord community link in Mainnet, Testnet, and configuration files

Copy link
Contributor

coderabbitai bot commented Jan 15, 2025

Walkthrough

The pull request involves updating Discord invite links across multiple documentation files and the Docusaurus configuration. The changes replace the generic https://discord.gg/evmos link with a more specific invite link https://discord.com/invite/evmos-809048090249134080. This modification ensures consistent and accurate Discord community access points throughout the Evmos documentation.

Changes

File Change Summary
docs/develop/mainnet.md Updated Discord community link
docs/validate/index.md Updated Discord community link
docs/validate/mainnet.mdx Updated Discord channel invite link for peer sharing
docs/validate/testnet.mdx Updated Discord channel invite link
docusaurus.config.js Updated footer Discord link

Poem

🐰 A Discord link, once vague and wide,
Now precise, with purpose tied!
From .gg to invite so clear,
Community connections draw near 🌐
A rabbit's hop through links so bright! 🚀

Finishing Touches

  • 📝 Generate Docstrings (Beta)

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

netlify bot commented Jan 15, 2025

Deploy Preview for dancing-hummingbird-242a98 ready!

Name Link
🔨 Latest commit fe446ff
🔍 Latest deploy log https://app.netlify.com/sites/dancing-hummingbird-242a98/deploys/6787db720a982e0008f2c043
😎 Deploy Preview https://deploy-preview-181--dancing-hummingbird-242a98.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@@ -74,6 +74,6 @@ An essential part of building a dApp is getting in touch with the community to s
start contributing to your project. This will not only help your dApp's visibility but might result in a new community
of users, that want to improve your dApp.

Head over to the [Evmos Discord](https://discord.gg/evmos) channel get in touch with the community and contributors and
Head over to the [Evmos Discord](https://discord.com/invite/evmos-809048090249134080) channel get in touch with the community and contributors and
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

All of these links should be a discord vanity url instead of this invite.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (1)
docs/develop/mainnet.md (1)

77-77: Fix line length to improve readability.

The line exceeds the recommended length of 120 characters. Consider breaking it into multiple lines.

-Head over to the [Evmos Discord](https://discord.com/invite/evmos-809048090249134080) channel get in touch with the community and contributors and
+Head over to the [Evmos Discord](https://discord.com/invite/evmos-809048090249134080) channel
+to get in touch with the community and contributors and
🧰 Tools
🪛 Markdownlint (0.37.0)

77-77: Expected: 120; Actual: 146
Line length

(MD013, line-length)

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between db0fe46 and fe446ff.

📒 Files selected for processing (5)
  • docs/develop/mainnet.md (1 hunks)
  • docs/validate/index.md (1 hunks)
  • docs/validate/mainnet.mdx (1 hunks)
  • docs/validate/testnet.mdx (2 hunks)
  • docusaurus.config.js (1 hunks)
✅ Files skipped from review due to trivial changes (3)
  • docs/validate/testnet.mdx
  • docs/validate/index.md
  • docs/validate/mainnet.mdx
🧰 Additional context used
🪛 Markdownlint (0.37.0)
docs/develop/mainnet.md

77-77: Expected: 120; Actual: 146
Line length

(MD013, line-length)

⏰ Context from checks skipped due to timeout of 90000ms (3)
  • GitHub Check: Redirect rules - dancing-hummingbird-242a98
  • GitHub Check: Header rules - dancing-hummingbird-242a98
  • GitHub Check: Pages changed - dancing-hummingbird-242a98
🔇 Additional comments (2)
docusaurus.config.js (1)

206-206: LGTM! Discord invite link follows the official format.

The updated Discord invite link follows the recommended format with a specific server ID, which is more reliable than the generic invite link.

Let's verify the consistency of Discord links across the codebase:

✅ Verification successful

✅ Discord invite links are consistent across the codebase

All Discord invite links have been updated to use the new format https://discord.com/invite/evmos-809048090249134080. No instances of the old format remain.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Search for any remaining old Discord links
rg -i "discord\.gg/evmos"

# Search for all Discord invite links to ensure consistency
rg -i "discord\.com/invite/evmos"

Length of output: 908

docs/develop/mainnet.md (1)

77-77: LGTM! Discord invite link is consistent.

The Discord invite link matches the update in docusaurus.config.js, maintaining consistency across the documentation.

🧰 Tools
🪛 Markdownlint (0.37.0)

77-77: Expected: 120; Actual: 146
Line length

(MD013, line-length)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant