docs: update the list of available APIs

[yoshi-code-bot]

Update the list of available APIs in the README.

[gemini-code-assist]

Summary of Changes

Hello, I'm Gemini Code Assist¹! 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 focuses on maintaining the accuracy and completeness of the project's documentation by updating the list of available APIs. It incorporates new services and corrects existing entries to ensure users have the most current information regarding client libraries and their respective resources.

Highlights

• New API Additions: Added 'Auth OAuthlib', 'Gemini Enterprise for Customer Experience API', and 'Workload Manager API' to the list of available libraries in the README.
• API Name and Link Updates: Updated the names and associated links for 'Datastore', 'Firestore', and 'Logging' APIs to reflect their current naming conventions and repository locations.
• PyPI Badge Definitions: Included new PyPI badge definitions for the recently added 'Auth OAuthlib', 'Gemini Enterprise for Customer Experience API', and 'Workload Manager API' to ensure their status is correctly displayed.

Changelog

• README.rst
  • Added 'Auth OAuthlib' to the Libraries section.
  • Updated 'Datastore' to 'Datastore API' and adjusted its repository link.
  • Updated 'Firestore' to 'Firestore API', modified its repository link, and standardized its client library issues link.
  • Updated 'Logging' to 'Logging API', modified its repository link, and standardized its client library issues link.
  • Added 'Gemini Enterprise for Customer Experience API' to the Libraries section.
  • Added 'Workload Manager API' to the Libraries section.
  • Included PyPI badge definitions for 'google-auth-oauthlib', 'google-cloud-ces', and 'google-cloud-workloadmanager'.

Activity

• No human activity has been recorded on this pull request yet.

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]

Code Review

This pull request updates the list of available APIs in the README file. It adds several new APIs, renames some for consistency, and updates corresponding links. The changes in the main library table are correctly sorted alphabetically. However, some of the new PyPI badge definitions at the end of the file are not in alphabetical order, which could affect maintainability. I've added comments to point out where these should be moved to maintain a sorted list.

[gemini-code-assist]

For better maintainability, the list of PyPI badge definitions should be kept in alphabetical order based on the package name. The google-auth-oauthlib definition should be placed before the google-cloud-assured-workloads definition (on line 1699).

[gemini-code-assist]

To maintain alphabetical order in the list of PyPI badge definitions, this definition for google-cloud-ces should be placed much earlier in the list. Based on its name, it should come before entries like google-cloud-gke-connect-gateway (on line 2071).