-
Notifications
You must be signed in to change notification settings - Fork 35
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
base: main
Are you sure you want to change the base?
Conversation
WalkthroughThe pull request involves updating Discord invite links across multiple documentation files and the Docusaurus configuration. The changes replace the generic Changes
Poem
Finishing Touches
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? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
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)
Other keywords and placeholders
CodeRabbit Configuration File (
|
✅ Deploy Preview for dancing-hummingbird-242a98 ready!
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 |
There was a problem hiding this comment.
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.
There was a problem hiding this 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
📒 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)
Summary by CodeRabbit
https://discord.gg/evmos
to specifichttps://discord.com/invite/evmos-809048090249134080