Skip to content

Add automatic labeling bot #4478

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
wants to merge 4 commits into
base: release/10.11
Choose a base branch
from

Conversation

poweiw
Copy link
Collaborator

@poweiw poweiw commented Jun 4, 2025

Adds an automatic labelling bot using LLM whenever an issue is raised. See an example issue at poweiw#4 and its run log at https://github.com/poweiw/TensorRT/actions/runs/15433437593

The goggles_action is still private. Please contact @poweiw for access.

This bot uses label descriptions defined in TRT repo, so ensure the labels descriptions are clear and instructive. Note that this bot DOES NOT auto-triage, so module owners still have to check their modules.

@poweiw poweiw marked this pull request as ready for review June 4, 2025 04:23
@poweiw poweiw requested a review from a team as a code owner June 4, 2025 04:23
@poweiw poweiw requested review from LeoZDong and akhilg-nv June 4, 2025 04:23
@akhilg-nv
Copy link
Collaborator

How is the LLM being queried? It seems to me like the labels on your sample issue don't necessarily match the existing pool of labels we have in the main repo, and I think we'd like it to do that for consistency and perhaps later auto-assigning based on the labels added.

@poweiw
Copy link
Collaborator Author

poweiw commented Jun 4, 2025

@akhilg-nv The labels are queried by the time the action was triggered. The labels are inconsistent to the labels we have in the main repo because the issue was raised in my fork. See the difference between labels in upstream and labels in my fork. Sent you the invitation to checkout the labeling logic

Copy link
Collaborator

@akhilg-nv akhilg-nv left a comment

Choose a reason for hiding this comment

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

@akhilg-nv The labels are queried by the time the action was triggered. The labels are inconsistent to the labels we have in the main repo because the issue was raised in my fork. See the difference between labels in upstream and labels in my fork. Sent you the invitation to checkout the labeling logic

Thanks, can we add a failsafe to make sure triaged label isn't applied incorrectly in the validation step? LGTM

@poweiw poweiw marked this pull request as draft June 14, 2025 00:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants