Skip to content

docs: standardize installation note for antigravity plugins#2373

Merged
twishabansal merged 9 commits into
mainfrom
twishabansal-patch-2
Jan 30, 2026
Merged

docs: standardize installation note for antigravity plugins#2373
twishabansal merged 9 commits into
mainfrom
twishabansal-patch-2

Conversation

@twishabansal

@twishabansal twishabansal commented Jan 27, 2026

Copy link
Copy Markdown
Contributor

Description

Should include a concise description of the changes (bug or feature), it's
impact, along with a summary of the solution

PR Checklist

Thank you for opening a Pull Request! Before submitting your PR, there are a
few things you can do to make sure it goes smoothly:

  • Make sure you reviewed
    CONTRIBUTING.md
  • Make sure to open an issue as a
    bug/issue
    before writing your code! That way we can discuss the change, evaluate
    designs, and agree on the general idea
  • Ensure the tests and linter pass
  • Code coverage does not decrease (if any source code was changed)
  • Appropriate docs were updated (if necessary)
  • Make sure to add ! if this involve a breaking change

🛠️ Fixes #<issue_number_goes_here>

@gemini-code-assist

Copy link
Copy Markdown
Contributor

Summary of Changes

Hello @twishabansal, 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 TOOLBOX_README.md documentation by providing crucial information regarding the installation and update mechanism of the toolbox server. It aims to inform users about the automatic nature of package updates and offers guidance for those who might prefer to manage specific versions manually, ensuring a clearer understanding of the installation process.

Highlights

  • Installation Behavior Clarification: Added a detailed note to the installation instructions explaining that the toolbox server npm package always installs the latest version, leading to automatic updates.
  • Version Management Guidance: Provided information on the implications of automatic updates (potential for unexpected changes) and offered an alternative to run the server manually for specific versions.
  • Documentation Structure Adjustment: Re-indexed the subsequent installation steps (from 2 and 3 to 3 and 4) to correctly incorporate the new note.
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.

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

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Code Review

The pull request updates the TOOLBOX_README.md file to include an important note regarding the installation process. The note clarifies that installation always uses the latest available npm package, ensuring users are up-to-date but also highlighting the potential for unexpected changes. The subsequent steps in the installation guide have been correctly renumbered to accommodate this new information. The changes are clear and improve the documentation for users.

@github-actions

Copy link
Copy Markdown
Contributor

@twishabansal twishabansal changed the title Update TOOLBOX_README.md docs: Standardize installation note and use @latest tag Jan 27, 2026
@github-actions

Copy link
Copy Markdown
Contributor

@twishabansal twishabansal marked this pull request as ready for review January 27, 2026 16:23
@twishabansal twishabansal requested a review from a team January 27, 2026 16:23
@twishabansal twishabansal changed the title docs: Standardize installation note and use @latest tag docs: Standardize installation note for antigravity plugins Jan 27, 2026
@github-actions

Copy link
Copy Markdown
Contributor

@twishabansal twishabansal changed the title docs: Standardize installation note for antigravity plugins docs: standardize installation note for antigravity plugins Jan 27, 2026
@github-actions

Copy link
Copy Markdown
Contributor

@github-actions

Copy link
Copy Markdown
Contributor

@github-actions

Copy link
Copy Markdown
Contributor

Comment thread docs/ALLOYDBPG_README.md Outdated
@github-actions

Copy link
Copy Markdown
Contributor

@twishabansal twishabansal merged commit e024594 into main Jan 30, 2026
11 of 13 checks passed
@twishabansal twishabansal deleted the twishabansal-patch-2 branch January 30, 2026 04:55
@github-actions

Copy link
Copy Markdown
Contributor

🧨 Preview deployments removed.

kshalu-code pushed a commit to kshalu-code/genai-toolbox that referenced this pull request Feb 4, 2026
…is#2373)

## Description

> Should include a concise description of the changes (bug or feature),
it's
> impact, along with a summary of the solution

## PR Checklist

> Thank you for opening a Pull Request! Before submitting your PR, there
are a
> few things you can do to make sure it goes smoothly:

- [x] Make sure you reviewed

[CONTRIBUTING.md](https://github.com/googleapis/genai-toolbox/blob/main/CONTRIBUTING.md)
- [ ] Make sure to open an issue as a

[bug/issue](https://github.com/googleapis/genai-toolbox/issues/new/choose)
  before writing your code! That way we can discuss the change, evaluate
  designs, and agree on the general idea
- [ ] Ensure the tests and linter pass
- [ ] Code coverage does not decrease (if any source code was changed)
- [ ] Appropriate docs were updated (if necessary)
- [ ] Make sure to add `!` if this involve a breaking change

🛠️ Fixes #<issue_number_goes_here>
nester-neo4j pushed a commit to nester-neo4j/genai-toolbox that referenced this pull request Feb 4, 2026
…is#2373)

## Description

> Should include a concise description of the changes (bug or feature),
it's
> impact, along with a summary of the solution

## PR Checklist

> Thank you for opening a Pull Request! Before submitting your PR, there
are a
> few things you can do to make sure it goes smoothly:

- [x] Make sure you reviewed

[CONTRIBUTING.md](https://github.com/googleapis/genai-toolbox/blob/main/CONTRIBUTING.md)
- [ ] Make sure to open an issue as a

[bug/issue](https://github.com/googleapis/genai-toolbox/issues/new/choose)
  before writing your code! That way we can discuss the change, evaluate
  designs, and agree on the general idea
- [ ] Ensure the tests and linter pass
- [ ] Code coverage does not decrease (if any source code was changed)
- [ ] Appropriate docs were updated (if necessary)
- [ ] Make sure to add `!` if this involve a breaking change

🛠️ Fixes #<issue_number_goes_here>
nester-neo4j pushed a commit to nester-neo4j/genai-toolbox that referenced this pull request Feb 4, 2026
…is#2373)

## Description

> Should include a concise description of the changes (bug or feature),
it's
> impact, along with a summary of the solution

## PR Checklist

> Thank you for opening a Pull Request! Before submitting your PR, there
are a
> few things you can do to make sure it goes smoothly:

- [x] Make sure you reviewed

[CONTRIBUTING.md](https://github.com/googleapis/genai-toolbox/blob/main/CONTRIBUTING.md)
- [ ] Make sure to open an issue as a

[bug/issue](https://github.com/googleapis/genai-toolbox/issues/new/choose)
  before writing your code! That way we can discuss the change, evaluate
  designs, and agree on the general idea
- [ ] Ensure the tests and linter pass
- [ ] Code coverage does not decrease (if any source code was changed)
- [ ] Appropriate docs were updated (if necessary)
- [ ] Make sure to add `!` if this involve a breaking change

🛠️ Fixes #<issue_number_goes_here>
dumians pushed a commit to dumians/genai-toolbox that referenced this pull request Feb 18, 2026
…is#2373)

## Description

> Should include a concise description of the changes (bug or feature),
it's
> impact, along with a summary of the solution

## PR Checklist

> Thank you for opening a Pull Request! Before submitting your PR, there
are a
> few things you can do to make sure it goes smoothly:

- [x] Make sure you reviewed

[CONTRIBUTING.md](https://github.com/googleapis/genai-toolbox/blob/main/CONTRIBUTING.md)
- [ ] Make sure to open an issue as a

[bug/issue](https://github.com/googleapis/genai-toolbox/issues/new/choose)
  before writing your code! That way we can discuss the change, evaluate
  designs, and agree on the general idea
- [ ] Ensure the tests and linter pass
- [ ] Code coverage does not decrease (if any source code was changed)
- [ ] Appropriate docs were updated (if necessary)
- [ ] Make sure to add `!` if this involve a breaking change

🛠️ Fixes #<issue_number_goes_here>
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.

3 participants