Skip to content

Conversation

@yoshi-code-bot
Copy link
Contributor

Update the list of available APIs in the README.

@yoshi-code-bot yoshi-code-bot requested review from a team as code owners February 10, 2026 07:27
@trusted-contributions-gcf trusted-contributions-gcf bot added the kokoro:force-run Add this label to force Kokoro to re-run the tests. label Feb 10, 2026
@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @yoshi-code-bot, 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's README.rst file to reflect the availability of several new Google Cloud Python client libraries. The changes ensure that the documentation accurately lists the latest APIs, along with their respective PyPI badges and issue tracking links, providing up-to-date information for users.

Highlights

  • New API Listings: Added entries for 'API Registry API', 'Audit Manager API', 'Auth httplib2', and 'Python Test Utils for Cloud' to the list of available libraries.
  • PyPI Badge Integration: Included corresponding PyPI badge definitions for the newly added APIs to display their version status.
Changelog
  • README.rst
    • Added 'API Registry API' to the Libraries section.
    • Added 'Audit Manager API' to the Libraries section.
    • Added 'Auth httplib2' to the Libraries section.
    • Added 'Python Test Utils for Cloud' to the Libraries section.
    • Included PyPI badge definitions for 'google-cloud-apiregistry', 'google-cloud-auditmanager', 'google-auth-httplib2', and 'google-cloud-testutils'.
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 updates the README.rst file to include several new APIs and helper libraries in the list of available packages. The changes are mostly correct, but there are a few places where the new entries are not added in alphabetical order, which impacts the maintainability of this documentation file. I've left comments on the specific lines where the ordering should be corrected.

Comment on lines +868 to +873
* - `API Registry API <https://github.com/googleapis/google-cloud-python/tree/main/packages/google-cloud-apiregistry>`_
- preview
- |PyPI-google-cloud-apiregistry|
- `API Issues <https://issuetracker.google.com/issues?q=componentid:1979613>`_
- `File an API Issue <https://issuetracker.google.com/issues/new?component=1979613&template=2231768>`_
- `Client Library Issues <https://github.com/googleapis/google-cloud-python/issues>`_
Copy link
Contributor

Choose a reason for hiding this comment

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

medium

The new entry for API Registry API is not in the correct alphabetical position. It is placed before Access Context Manager, but it should come after it to maintain the alphabetical sorting of the library list.

References
  1. Lists, such as this list of libraries, should be kept in alphabetical order to improve readability and maintainability. This is analogous to the general rule about programmatically sorting dictionary keys.

Comment on lines +1901 to +1902
.. |PyPI-google-cloud-apiregistry| image:: https://img.shields.io/pypi/v/google-cloud-apiregistry.svg
:target: https://pypi.org/project/google-cloud-apiregistry
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 new badge definition for PyPI-google-cloud-apiregistry is not in the correct global alphabetical position. For instance, it's placed before PyPI-google-cloud-access-context-manager, which should appear much earlier in the list. To improve maintainability, please place new entries in their correct alphabetical position.

References
  1. Lists, such as this list of badge definitions, should be kept in alphabetical order to improve readability and maintainability. This is analogous to the general rule about programmatically sorting dictionary keys.

Comment on lines +2107 to +2108
.. |PyPI-google-cloud-testutils| image:: https://img.shields.io/pypi/v/google-cloud-testutils.svg
:target: https://pypi.org/project/google-cloud-testutils
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 new badge definition for PyPI-google-cloud-testutils is not in the correct alphabetical position. It is placed before PyPI-google-cloud-quotas, but should come after it. For better maintainability, this list of definitions should be kept in alphabetical order.

References
  1. Lists, such as this list of badge definitions, should be kept in alphabetical order to improve readability and maintainability. This is analogous to the general rule about programmatically sorting dictionary keys.

@parthea parthea merged commit ce29682 into googleapis:main Feb 10, 2026
27 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

kokoro:force-run Add this label to force Kokoro to re-run the tests.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants