[GitHub] Classify template issues by issue type - #461
Merged
Conversation
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
There was a problem hiding this comment.
Pull request overview
This PR updates GitHub issue form templates to classify new issues using GitHub issue types (e.g., Bug 🐛, Feature 📬) instead of relying on the legacy classification labels, and replaces the old “unverified” state label with the newer “needs triage” label.
Changes:
- Set
type: Bug 🐛in the bug report template andtype: Feature 📬in the feature request template. - Remove legacy classification labels from templates and apply
needs triage 🔍on submission (per PR intent). - Remove
unverified ⌛from the documentation template.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| .github/ISSUE_TEMPLATE/feature_request.yml | Adds issue type for feature requests and switches arrival label to needs triage 🔍. |
| .github/ISSUE_TEMPLATE/bug_report.yml | Adds issue type for bug reports and switches arrival label to needs triage 🔍. |
| .github/ISSUE_TEMPLATE/documentation-issue.yml | Removes unverified ⌛ from documentation issues (but currently does not apply needs triage 🔍). |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Comment on lines
3
to
4
| labels: | ||
| - documentation 📃 |
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.
Summary of the Pull Request
What is this about: Issue templates classify a new issue by label, while the organization now provides issue types.
Description:
bug_report.ymlsetstype: Bug 🐛andfeature_request.ymlsetstype: Feature 📬, matching the templates inLookupEngineandLookupEngine.UI.The
bug 🐛,feature request 📬, andimprovements ✨labels leave the templates; the type carries the classification.Every template now applies
needs triage 🔍on arrival in place ofunverified ⌛, which named the same state under an older name.documentation-issue.ymlkeepsdocumentation 📃and takes no type.The 62 existing issues that carried these labels already have the matching type set.
Quality Checklist