Remove auto-labels from issue templates#12972
Merged
Conversation
The bug_report, submit-a-request, and submit-a-design-proposal issue templates currently auto-apply 'bug' and 'enhancement' labels. This causes issues to arrive pre-labeled with types that may not be accurate, making triage harder since the template-applied labels can't be trusted. Removing auto-labels ensures all type classification happens during triage, giving the team confidence that labeled issues have been reviewed. Co-authored-by: Copilot <[email protected]>
Contributor
There was a problem hiding this comment.
Pull request overview
Removes template-assigned type labels from legacy GitHub Markdown issue templates so that issue type classification happens during triage rather than at submission time.
Changes:
- Removed the default
enhancementlabel from the “Submit a request” template. - Removed the default
enhancementlabel from the “Submit a design proposal” template. - Removed the default
buglabel from the “Bug report” template.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| .github/ISSUE_TEMPLATE/submit-a-request.md | Stops auto-applying enhancement to new “request” issues. |
| .github/ISSUE_TEMPLATE/submit-a-design-proposal.md | Stops auto-applying enhancement to new “design proposal” issues. |
| .github/ISSUE_TEMPLATE/bug_report.md | Stops auto-applying bug to new “bug report” issues. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
BagToad
approved these changes
Mar 19, 2026
Member
BagToad
left a comment
There was a problem hiding this comment.
Yup lgtm. Let's see how this goes!
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
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.
Problem
The
bug_report,submit-a-request, andsubmit-a-design-proposalissue templates currently auto-applybugandenhancementlabels respectively. This means issues arrive pre-labeled with type classifications that may not be accurate — an issue filed as a "bug" might actually be an enhancement, and vice versa.During FR triage, these template-applied labels can't be trusted, making it harder to distinguish between issues that have been properly triaged and those that just have auto-applied labels.
Solution
Remove the auto-applied labels from all three issue templates:
bug_report.md: removedbuglabelsubmit-a-request.md: removedenhancementlabelsubmit-a-design-proposal.md: removedenhancementlabelThis ensures all type classification happens during triage, giving the team confidence that labeled issues have actually been reviewed.