Skip to content

Conversation

@jcstein
Copy link
Member

@jcstein jcstein commented Dec 15, 2025

Overview

@gemini-code-assist
Copy link
Contributor

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 updates the client documentation by removing references to client libraries that are no longer current or actively maintained. The goal is to ensure that the documentation accurately reflects the available and supported methods for interacting with the Celestia Node API, providing users with up-to-date resources.

Highlights

  • Documentation Cleanup: Removed documentation for the Python client, which was identified as outdated.
  • Documentation Cleanup: Removed documentation for the TypeScript client, which was identified as outdated.
  • Formatting Update: Adjusted the casing of 'Official Clients' and 'Community Clients' headings for consistency.
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

  1. 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.

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request cleans up the documentation by removing outdated community client libraries. The changes are straightforward. I've added two minor suggestions to maintain stylistic consistency in the markdown headings.

Celestia Node API can be accessed through various client libraries in different programming languages.

## Official Clients
## Official clients
Copy link
Contributor

Choose a reason for hiding this comment

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

medium

This change to sentence case introduces a stylistic inconsistency within this file. Other headings, such as ## Getting Started and the ### level headings, use Title Case. For consistency within this document, it would be better to keep this as ## Official Clients.

## Official Clients

- **Tutorial**: [Go Client Tutorial](/build/post-retrieve-blob/client/go/) - Learn how to submit and retrieve blobs without running your own node

## Community Clients
## Community clients
Copy link
Contributor

Choose a reason for hiding this comment

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

medium

Similar to the heading on line 5, changing this to sentence case makes it inconsistent with other headings in the file that use Title Case. To maintain a consistent style throughout this document, please revert this to ## Community Clients.

## Community Clients

Copy link
Member Author

Choose a reason for hiding this comment

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

they should all be sentence

Base automatically changed from docs-glow-up to main December 16, 2025 15:13
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.

2 participants