chore: drop labels: ["triage"] from issue templates#4918
Merged
aglinxinyuan merged 1 commit intoMay 4, 2026
Conversation
PR apache#4899 retired the `triage` label workflow in favor of the search filter `is:issue is:open no:assignee`. New issues opened from the bug, task, or feature templates were still attaching `triage` automatically because each template carried `labels: ["triage"]` at the top. Drop the line in all three templates so newly opened issues match the no-assignee filter directly. Existing issues that already carry the label are unaffected by this change; they will be cleaned up by a one-shot label deletion after this lands.
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #4918 +/- ##
============================================
- Coverage 42.04% 42.03% -0.01%
+ Complexity 2156 2154 -2
============================================
Files 980 980
Lines 36292 36292
Branches 3783 3783
============================================
- Hits 15258 15256 -2
+ Misses 20112 20110 -2
- Partials 922 926 +4
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
aglinxinyuan
approved these changes
May 4, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changes were proposed in this PR?
Follow-up to PR #4899, which retired the
triagelabel workflow in favor of the search filteris:issue is:open no:assignee. The three issue templates still carriedlabels: ["triage"]at the top, so every new issue opened via the templates re-acquired the label even though no workflow consumes it anymore.Drop the line in
bug-template.yaml,task-template.yaml, andfeature-template.yaml(one line each).Any related issues, documentation, discussions?
Closes #4917. Sequel to #4899.
After this lands, the
triagelabel itself can be deleted from the repo:That removes the chip from every issue that still carries it.
How was this PR tested?
YAML parse on all three templates. Behavior verifiable post-merge by opening a new issue from any template and confirming no
triagelabel is attached.Was this PR authored or co-authored using generative AI tooling?
Generated-by: Claude Opus 4.7 (1M context)