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 aims to streamline label management by eliminating redundant label definitions within the repository's .github/labels.yaml file. It aligns with an organizational effort to centralize common labels, ensuring that only repository-specific labels remain in this file, thereby reducing duplication and simplifying maintenance.

Highlights

• Label Centralization: Removed common labels from .github/labels.yaml that are now centrally managed in .github/labels.common.yaml.
• Repository-Specific Labels: Ensured that .github/labels.yaml now only contains labels unique to this repository.
• File Formatting: Preserved the trailing newline at the end of the .github/labels.yaml file.

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 .github/labels.yaml to centralize their management, which is a good improvement. The changes align with the PR's goal. One point of feedback: the resulting file lacks a trailing newline. It's a strong convention to end text files with a newline character to ensure compatibility with various command-line tools and prevent issues in some version control views. Please consider adding a newline to the end of .github/labels.yaml.