docs: add status pages to participate page that has all networks on it #2238
Conversation
![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 @jcstein, 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 enhances the documentation by integrating direct links to the status pages for Celestia's Mainnet Beta, Arabica devnet, and Mocha testnet into the participate.md guide. This change aims to provide users with quick and easy access to the operational status of each network. The author also raises questions regarding the active maintenance and current state of the Arabica and Mocha status pages, highlighting potential discrepancies or issues that may require attention.
Highlights
- Documentation Update: Added a link to the official Celestia Mainnet Beta status page within the
how-to-guides/participate.mdfile, providing users with direct access to network health information. - Documentation Update: Incorporated a link to the official Celestia Arabica devnet status page in
how-to-guides/participate.md, enhancing visibility into the devnet's operational status. - Documentation Update: Included a link to the official Celestia Mocha testnet status page in
how-to-guides/participate.md, allowing users to easily monitor the testnet's condition.
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 by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.
| 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 pull request 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 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. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.
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 helpful links to the network status pages on the main participate.md page. My review includes suggestions to wrap these links in dedicated subheadings to improve the document's structure and maintain consistency with how status links are presented on other pages. This will make the information easier to find and the document easier to navigate.
| See the [official Celestia Mainnet Beta status page](https://status.celestia.dev/status/mainnet). | ||
|
|
There was a problem hiding this comment.
For better document structure and consistency with other pages like mainnet.md, it would be clearer to place this link under a dedicated heading.
| See the [official Celestia Mainnet Beta status page](https://status.celestia.dev/status/mainnet). | |
| ### Network status | |
| See the [official Celestia Mainnet Beta status page](https://status.celestia.dev/status/mainnet). |
| See the [official Celestia Arabica devnet status page](https://status.celestia.dev/status/arabica). | ||
|
|
There was a problem hiding this comment.
To improve document structure and consistency, consider adding a dedicated heading for the status page link. Since "Arabica Devnet" is a level 3 heading, this new subheading should be level 4.
| See the [official Celestia Arabica devnet status page](https://status.celestia.dev/status/arabica). | |
| #### Network status | |
| See the [official Celestia Arabica devnet status page](https://status.celestia.dev/status/arabica). |
| See the [official Celestia Mocha testnet status page](https://status.celestia.dev/status/mocha). | ||
|
|
There was a problem hiding this comment.
For consistency with the other sections, this link should be placed under its own "Network status" heading. As "Mocha testnet" is a level 3 heading, the new subheading should be level 4 to maintain a logical document hierarchy.
| See the [official Celestia Mocha testnet status page](https://status.celestia.dev/status/mocha). | |
| #### Network status | |
| See the [official Celestia Mocha testnet status page](https://status.celestia.dev/status/mocha). |
Overview
@sysrex are these status pages actively maintained?