chore: remove build badges

[suztomo]

Removes old badge references.

b/468377909

[gemini-code-assist]

Summary of Changes

Hello @suztomo, 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 tidying up the project's README.md by eliminating outdated and irrelevant build status badges. The change removes a dedicated 'CI Status' section and its underlying image and link references, ensuring the documentation remains current and free of stale information.

Highlights

• Documentation Cleanup: Removed the 'CI Status' section from the README.md file, which previously displayed build statuses for different Java versions.
• Outdated Badge References: Deleted all associated kokoro-badge-image and kokoro-badge-link definitions that were no longer in use, streamlining the README's content.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

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 aims to remove old build badge references from the README.md file. While the removal of the CI status table and its associated links is correct, the change also removes the link definition for javadocs, which appears to be unintentional. This breaks two important documentation links within the file. I have added a comment to highlight this issue.

[gemini-code-assist]

The removal of the javadocs link definition seems unintentional as it's not related to the CI build badges. This change breaks the 'Client Library Documentation' link on line 9 and another reference on line 96. Please restore this link definition to ensure the documentation links remain functional.

[suztomo]

Closing because automation (cloud-java-bot) overwritten the changes and the PR now has an empty diff.