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 change centralizes the management of these common labels in .github/labels.common.yaml, thereby eliminating duplication and establishing a clear distinction between universally applicable labels and those specific to the repository. This improves maintainability and consistency in label usage.

Highlights

• Centralized Label Management: Common labels are now exclusively managed 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, providing a cleaner and more organized structure for label management.

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 label definitions from .github/labels.yaml to avoid redundancy with a new common labels file. This is a good refactoring for maintainability. I have one suggestion regarding a leftover comment to make the resulting configuration even cleaner.

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

.github/labels.yaml (2-57)

Removing these duplicated labels is a good refactoring. However, this change leaves the section comment # Warning from line 1 as a dangling comment in the file. To improve clarity, consider also removing this line, leaving the file empty if no repository-specific labels are currently needed. This would prevent confusion for future contributors.