fix: use the existing enhancement label in the feature request template - #44
Merged
Merged
Conversation
feature-request.yml assigned labels: ["Feature request"], which is not a
label on this repository. The CLI refuses it outright ("could not add
label: 'Feature request' not found", hit while filing #40); the web form
drops an unknown label silently, so an issue opened there would land
unlabelled with no indication anything went wrong.
Reuse `enhancement`, which already exists and is what #40 ended up
carrying, rather than creating a second label meaning the same thing.
Closes #41
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
There was a problem hiding this comment.
🟢 Approval recommended
The change is minimal, matches the repo’s existing labels, and resolves the misconfigured issue template without impacting runtime code.
Pull request overview
This PR fixes repository configuration so that feature requests created via GitHub’s “Feature Request” issue form are automatically labeled with an existing label (enhancement) instead of a non-existent one (Feature request). This aligns the template with the repository’s actual label set and ensures feature requests don’t land unlabelled.
Changes:
- Update the Feature Request issue template to apply
labels: ["enhancement"]instead oflabels: ["Feature request"].
File summaries
| File | Description |
|---|---|
| .github/ISSUE_TEMPLATE/feature-request.yml | Switches the default applied label to an existing repository label so new feature-request issues are correctly tagged. |
Review details
- Files reviewed: 1/1 changed files
- Comments generated: 0
- Review effort level: Lite
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
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
.github/ISSUE_TEMPLATE/feature-request.ymlassignedlabels: ["Feature request"], a label that does not exist on this repository, so issues opened through the Feature Request form land unlabelled.Why
enhancementrather than a new labelThe repo already has
enhancement, and it is what #40 ended up carrying after the CLI refused the templated label. Creating a second label meaning "feature request" would need a convention to keep the two untangled; reusing the existing one keeps it at one label per concept.Verification
gh api repos/whats2000/isaacsim-mcp-server/labels --jq '.[].name'listsenhancementand does not listFeature request.bug-report.ymlwas already correct (labels: ["bug"]);config.ymlassigns no labels. This was the only template affected.Repository configuration only — no package code changes, so no CHANGELOG entry (a user of 0.6.1 cannot hit this) and no live Isaac Sim sweep applies.
Closes #41
🤖 Generated with Claude Code