docs: add celestiahub by NODERS to explorers list#2112
docs: add celestiahub by NODERS to explorers list#2112StanislavOdnorog wants to merge 1 commit intocelestiaorg:mainfrom
Conversation
Updated the mainnet explorers list, added celestiahub by NODERS LLC
WalkthroughA new URL for a Mainnet Beta explorer ("https://celestiahub.org/explorer") was added at the top of the explorers list in the documentation file. No other edits or changes to logic, structure, or exported entities were made. Changes
Sequence Diagram(s)Possibly related PRs
Suggested reviewers
Poem
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. 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 (
|
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Summary of Changes
Hello @StanislavOdnorog, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!
This pull request updates the project documentation by adding a new blockchain explorer to the existing list of Mainnet Beta explorers. This change aims to provide users with an additional resource for network exploration, enhancing the comprehensiveness of the how-to-guides.
Highlights
- Documentation Update: Added
celestiahub.org/explorerto the list of Mainnet Beta explorers in thehow-to-guides/mainnet.mdfile.
Using Gemini Code Assist
The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.
Invoking Gemini
You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.
| Feature | Command | Description |
|---|---|---|
| Code Review | /gemini review |
Performs a code review for the current pull request in its current state. |
| Pull Request Summary | /gemini summary |
Provides a summary of the current pull request in its current state. |
| Comment | @gemini-code-assist | Responds in comments when explicitly tagged, both in issue comments and review comments. |
| Help | /gemini help |
Displays a list of available commands. |
Customization
To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.
Limitations & Feedback
Gemini Code Assist is currently in preview and may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments to provide feedback.
You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.
Footnotes
-
Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩
There was a problem hiding this comment.
Code Review
This pull request adds a new explorer, CelestiaHub by NODERS, to the list of Mainnet Beta explorers in how-to-guides/mainnet.md. The change itself is a simple addition of a markdown link.
My primary feedback is a medium severity suggestion to consider alphabetically sorting the entire list of explorers. This aligns with general best practices for documentation, aiming to improve maintainability and user experience by making the list easier to scan and update as more explorers are added over time.
|
|
||
| There are multiple explorers you can use for Mainnet Beta: | ||
|
|
||
| - [https://celestiahub.org/explorer](https://celestiahub.org/explorer) |
There was a problem hiding this comment.
Thank you for adding CelestiaHub to the list of explorers.
The current list of explorers (lines 224-233 in the updated file) does not appear to follow a specific order (e.g., alphabetical). For better readability and long-term maintainability, especially as this list grows, consider sorting all entries alphabetically by the explorer's name or primary domain.1
For instance, in an alphabetized list, celestiahub.org would be placed after celestia.valopers.com and before celenium.io.
While this would involve reordering existing lines beyond this specific addition, adopting a consistent sorting convention would be beneficial. If a full sort is outside the scope of this PR, that's understandable, but it's a good point for future list maintenance.
Style Guide References
Footnotes
-
Alphabetical sorting of lists is a common best practice in documentation. It improves scannability, makes it easier to locate items, and simplifies the process of adding new items consistently, reducing potential merge conflicts or uncertainty about placement in a collaborative environment. ↩
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (1)
how-to-guides/mainnet.md (1)
224-224: Consider adding a descriptive label for the explorer entry
Right now the link text is just the URL. To improve readability, you could replace it with a name like “CelestiaHub (by NODERS)”. For example:- - [https://celestiahub.org/explorer](https://celestiahub.org/explorer) + - [CelestiaHub (by NODERS)](https://celestiahub.org/explorer)
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
how-to-guides/mainnet.md(1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (2)
- GitHub Check: deploy-preview
- GitHub Check: build
🔇 Additional comments (1)
how-to-guides/mainnet.md (1)
224-224: Verify the new explorer URL is reachable and correct
Please ensure thathttps://celestiahub.org/explorerreturns a valid response (e.g., 200 OK) and navigates to the intended explorer UI.
1 participant
Overview
Updated the mainnet explorers list in how-to-guided, added celestiahub.org app by NODERS validator
Summary by CodeRabbit