Remove common labels from labels.yaml

[posquit0]

Remove labels that are defined in .github/labels.common.yaml from .github/labels.yaml to avoid duplication.

This change ensures that:

• Common labels are managed centrally in labels.common.yaml
• Repository-specific labels remain in labels.yaml
• No duplicate label definitions exist

[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 refactors the repository's label configuration by removing common label definitions from .github/labels.yaml. The primary goal is to eliminate duplication and centralize the management of shared labels within .github/labels.common.yaml, thereby ensuring a cleaner and more organized approach to label management.

Highlights

• Centralized Label Management: Common labels are now managed exclusively in .github/labels.common.yaml, promoting a single source of truth for shared label definitions.
• Reduced Duplication: Duplicate label definitions have been removed from .github/labels.yaml, ensuring that each label is defined only once across the repository's configuration.
• Clearer Separation of Concerns: The .github/labels.yaml file is now dedicated to repository-specific labels, improving clarity and maintainability by distinguishing them from common labels.

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 duplicated labels from .github/labels.yaml to centralize them in a common file. This is a good step towards better configuration management. My review contains one point of feedback regarding a leftover comment in the file to improve maintainability.

I am having trouble creating individual review comments. Click here to see my feedback.

.github/labels.yaml (2-57)

With the removal of these labels, the # Warning comment on line 1 is now a remnant that is out of context. This could be confusing for future contributors. To improve clarity, I suggest either removing the line to leave the file empty, or replacing it with a more descriptive comment. For example:

# This file is for repository-specific labels.
# Common labels are defined in .github/labels.common.yaml.

If this file is no longer needed at all, deleting it would be an even cleaner solution.