Two patches

[cgwalters]

README: Simplify and consolidate content

Remove verbose sections and redundant explanations. Consolidate the
table of contents into a concise 'What's Here' section. Trim the
Renovate documentation to essential information while keeping the
config example for maintainers.

Assisted-by: OpenCode (Claude Sonnet 4)
Signed-off-by: Colin Walters walters@verbum.org

---

docs: Add SOP for new repository setup

Document the standard steps for onboarding new repositories:

• Adding the maintainers team with Maintain permission
• Configuring Renovate to inherit the shared config
• Post-setup verification checklist

Assisted-by: OpenCode (Claude Sonnet 4)
Signed-off-by: Colin Walters walters@verbum.org

---

[gemini-code-assist]

Summary of Changes

Hello @cgwalters, 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 enhances the project's documentation by simplifying the main README.md for improved clarity and conciseness. Concurrently, it introduces a new Standard Operating Procedure document, providing clear, step-by-step guidance for onboarding and configuring new repositories, ensuring consistency across the organization.

Highlights

• README Simplification: The README.md has been significantly streamlined, removing verbose sections and consolidating information for better readability and conciseness.
• New Repository SOP: A new Standard Operating Procedure (docs/SOP-new-repository.md) has been added to guide the setup of new repositories within the organization, covering team permissions and Renovate configuration.

🧠 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 introduces two valuable documentation improvements. The README.md is significantly simplified and consolidated, making it much easier to read and navigate. The new Standard Operating Procedure for setting up new repositories is a great addition that will help standardize onboarding. My review found a couple of broken links in the new documentation, for which I've provided suggestions to fix them. Overall, these are excellent changes.

[gemini-code-assist]

The relative link to the Actions tab is incorrect. A relative link from the root README.md like ../../... will not resolve correctly. It's better to use a full URL to the workflow's Action page, which is more stable and user-friendly. This also makes it consistent with the link in the new SOP-new-repository.md document.

Suggested change

	Trigger Renovate manually from the [Actions tab](../../actions/workflows/renovate.yml)
	Trigger Renovate manually from the [Actions tab](https://github.com/bootc-dev/infra/actions/workflows/renovate.yml)

[gemini-code-assist]

The relative link to renovate-shared-config.json is broken. Since this document is in the docs/ directory, the link should point one level up to the repository root where the file is located.

Suggested change

	[renovate-shared-config.json](renovate-shared-config.json) to avoid
	[renovate-shared-config.json](../renovate-shared-config.json) to avoid