Skip to content

[misc] Add labeler for automatic labeling#12710

Merged
zhyncs merged 4 commits intomainfrom
chang/labeler
Nov 5, 2025
Merged

[misc] Add labeler for automatic labeling#12710
zhyncs merged 4 commits intomainfrom
chang/labeler

Conversation

@CatherineSue
Copy link
Copy Markdown
Collaborator

Motivation

This PR adds a labeler.yml to github so it can automatically assigns labels to a PR based on changed files.

Modifications

  • Add labeler.yml

Accuracy Tests

Benchmarking and Profiling

Checklist

@gemini-code-assist
Copy link
Copy Markdown
Contributor

Summary of Changes

Hello @CatherineSue, I'm Gemini Code Assist1! 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 integrates a new automated labeling system into the repository's GitHub workflow. By adding a labeler.yml configuration, pull requests will now automatically receive relevant labels based on the specific files and directories that have been modified. This enhancement is designed to improve the organization and discoverability of changes, making it easier for reviewers and contributors to quickly understand the scope and impact of each pull request.

Highlights

  • Automated PR Labeling: Introduced a new GitHub Actions configuration file, labeler.yml, to automatically assign labels to pull requests based on the files changed.
  • Comprehensive Label Definitions: Defined a wide range of labels covering different components and features, including router, sgl-kernel, documentation, dependencies, Multi-modal, lora, quant, performance, speculative-decoding, amd, deepseek, and hicache.
  • Improved Workflow Efficiency: This automation aims to streamline the pull request review process by ensuring PRs are consistently and accurately categorized.
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.

Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request introduces a GitHub labeler configuration, which is a valuable addition for automating the labeling of pull requests. The configuration is well-structured. I have a couple of suggestions to enhance consistency and ensure comprehensive coverage for labeling.

Comment thread .github/labeler.yml
Comment thread .github/labeler.yml
@zhyncs
Copy link
Copy Markdown
Collaborator

zhyncs commented Nov 5, 2025

@CatherineSue @slin1237 this looks good, we can merge first and iterate later, wdyt

@CatherineSue
Copy link
Copy Markdown
Collaborator Author

@zhyncs agree

@zhyncs zhyncs merged commit 83b104e into main Nov 5, 2025
25 checks passed
@zhyncs zhyncs deleted the chang/labeler branch November 5, 2025 22:44
Copy link
Copy Markdown

@luismiguelmariano77-hash luismiguelmariano77-hash left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Kd,'lom

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants