group badges together under slogan

[ofershap]

Summary

• Move small status badges below the big action buttons
• Slogan sits right after the title, action buttons follow, status badges last

Test plan

• Preview README on GitHub

Made with Cursor

[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 refines the presentation of the project's README.md file. The primary goal is to enhance the visual flow and prominence of key information by strategically repositioning elements such as the project slogan and various status badges. This adjustment aims to provide a clearer and more intuitive introduction to the project for new visitors.

Highlights

• README.md Structure: The layout of the README.md file has been reorganized to improve readability and information hierarchy.
• Badge Placement: Small status badges, previously located near the main title, have been relocated to appear after the primary action buttons.
• Slogan Position: The project slogan is now positioned immediately after the main title, preceding the action buttons and status badges.

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

Changelog

• README.md
  • Moved the block of status badges from directly below the main title to below the action buttons.
  • Ensured the project slogan is placed immediately after the main title.

Activity

• No 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 layout of the README.md file by moving the status badges to a new position. The change is cosmetic and achieves the stated goal of regrouping the badges. I have one suggestion to improve the consistency of the license link.

_{Note: Security Review has been skipped due to the limited scope of the PR.}

[gemini-code-assist]

The link for the license badge points to an external site (opensource.org), while the license link at the bottom of the README points to the LICENSE file within this repository. For consistency, it would be better if the badge also linked to the local LICENSE file.

Suggested change

	<a href="https://opensource.org/licenses/MIT"><img src="https://img.shields.io/badge/License-MIT-yellow.svg" alt="License: MIT" /></a>
	<a href="LICENSE"><img src="https://img.shields.io/badge/License-MIT-yellow.svg" alt="License: MIT" /></a>