chore: remove common labels from labels.yaml

[posquit0]

This PR removes labels that are defined in .github/labels.common.yaml from the repository-specific .github/labels.yaml file.

The common labels are now managed centrally and should not be duplicated in individual repository label files.

Changes:

• Removed labels that are already defined in .github/labels.common.yaml
• Kept only repository-specific labels in .github/labels.yaml
• Maintained trailing newline at the end of the file

This is part of the effort to centralize common label management across the organization.

[gemini-code-assist]

Summary of Changes

Hello @posquit0, 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 streamlines label management by removing common labels from the repository-specific .github/labels.yaml file. This change ensures that only unique, repository-specific labels reside in this file, preventing duplication with centrally managed common labels and supporting an organization-wide effort to centralize label definitions.

Highlights

• Label Centralization: Common labels previously duplicated in .github/labels.yaml have been removed, aligning with the centralized label management strategy.
• Repository-Specific Labels: The .github/labels.yaml file now exclusively contains labels unique to this repository, enhancing clarity and reducing redundancy.
• File Formatting: The trailing newline at the end of the .github/labels.yaml file has been preserved to maintain consistent file formatting.

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 correctly removes common labels from the repository-specific labels.yaml file, aligning with the goal of centralizing label management. My review includes a suggestion to further clean up the file by removing the now-empty section headers for better maintainability.

[gemini-code-assist]

Since all the labels under the Warning, Highlight, Cancel, and Size sections have been removed, these comment headers are now redundant. To improve the file's clarity and remove clutter, it would be best to remove these now-empty sections as well.