-
Notifications
You must be signed in to change notification settings - Fork 10.8k
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
[Github] Improve automatic new issue labelling #65309
Conversation
This patch: * Replace andymckay/labeler which does not appear to be maintained by github official solution * Remove the closed issue workflow which was disabled a few years ago and never fixed. * Add a few rules to add label based on PR title, hopefully that can make triaging simpler. If that turns out to be useful, we can consider adding more rules for backends, etc. We could technically also pattern match the body of the issue but I'm concerned about trying to be _too_ clever. The new system is only triggered on PR open so manual labels should not be removed. Full disclosure, this was not tested, not sure how testing could be done.
Full disclosure, this was not tested, not sure how testing could be done. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There are keywords to recognize backends (e.g. AArch64
, NVPTX
, AMDGPU
) and LLVM components (e.g. SelectionDAG
, SelectionDAGISel
, AsmParser
). I think they are worth listing here.
@Endilll are you happy adding more rules in a separate commit? |
Yes. I'm sorry I haven't read PR description attentively enough before submitting a review. |
This patch: * Replaces `andymckay/labeler` which does not appear to be maintained by github official solution * Removes the closed issue workflow which was disabled a few years ago and never fixed. * Adds a few rules to add label based on PR title, hopefully that can make triaging simpler. If that turns out to be useful, we can consider adding more rules for backends, etc. We could technically also pattern match the body of the issue but I'm concerned about trying to be _too_ clever. The new system is only triggered on PR open so manual labels should not be removed.
This patch:
andymckay/labeler
which does not appear to be maintained by github official solutionThe new system is only triggered on PR open so manual labels should not be removed.