docs: fix Contributors TOC anchor in v0.21.0 release notes

[ziggie1984]

Summary

The TOC link for the Contributors section in
docs/release-notes/release-notes-0.21.0.md pointed to #contributors,
but GitHub generates the anchor for # Contributors (Alphabetical Order) as #contributors-alphabetical-order, leaving the link broken
when the rendered file is viewed on GitHub.

This updates the TOC to use the working anchor, matching the form
already used in release-notes-0.18.0.md.

Test plan

• Open the rendered file on GitHub and click the Contributors entry in the TOC — it now jumps to the section.

[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 resolves an issue where the Table of Contents entry for the Contributors section in the v0.21.0 release notes did not correctly navigate to its target when viewed on GitHub. By updating the internal anchor to match GitHub's rendering convention, the documentation now functions as expected, improving user experience for those reviewing the release notes.

Highlights

• Documentation Fix: Corrected a broken Table of Contents (TOC) link in the v0.21.0 release notes documentation.
• Anchor Update: The anchor for the 'Contributors (Alphabetical Order)' section was updated from #contributors to the GitHub-generated #contributors-alphabetical-order.

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

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 table of contents in the version 0.21.0 release notes by correcting the anchor link for the contributors section to match its heading. I have no feedback to provide.

[saubyk]

ack

[github-actions]

PR Severity: LOW -- Auto-classified | 1 file | 2 lines changed -- docs/release-notes/release-notes-0.21.0.md - release notes doc update. LOW severity: only a markdown release notes file changed, no source code. No bump: 1 file (threshold >20), 2 lines (threshold >500). To override add severity-override-{critical,high,medium,low} label. <!-- pr-severity-bot -->

[github-actions]

Successfully created backport PR for v0.21.x-branch:

• [v0.21.x-branch] Backport #10776: docs: fix Contributors TOC anchor in v0.21.0 release notes #10778