chore(framework): type issues instead of labelling them#422
Merged
Conversation
The forms applied `labels: ["bug"]` and `labels: ["enhancement"]`, but neither label existed on GitHub, so every issue created through them landed unlabelled: zero of the repo's 300 issues carries one. Issue types (Bug, Feature, Task) are defined at the org level and the forms can set them directly. - Both forms swap `labels:` for `type:` and scope their title prefix, matching the scope commitlint already expects on the commit. - New `roadmap.yml` for maintainer-authored work: Problem, Scope, Acceptance criteria, and two optional sections that catch duplicates before they ship. - `labels.yml` keeps only what a bot or a human actually reads. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
1 task
blafourcade
added a commit
that referenced
this pull request
Jul 10, 2026
The forms applied `labels: ["bug"]` and `labels: ["enhancement"]`, but neither label existed on GitHub, so every issue created through them landed unlabelled: zero of the repo's 300 issues carries one. Issue types (Bug, Feature, Task) are defined at the org level and the forms can set them directly. - Both forms swap `labels:` for `type:` and scope their title prefix, matching the scope commitlint already expects on the commit. - New `roadmap.yml` for maintainer-authored work: Problem, Scope, Acceptance criteria, and two optional sections that catch duplicates before they ship. - `labels.yml` keeps only what a bot or a human actually reads. Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
Merged
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.
🎯 What & why
The issue forms applied
labels: ["bug"]andlabels: ["enhancement"]. Neither label exists on GitHub, so both directives were silently dropped: zero of the repo's 300 issues carries either one. Issue types (Bug,Feature,Task) are defined at the org level, and issue forms support a top-leveltype:key.🛠️ How it works
labels:fortype:. bug_report.yml setstype: Bug, feature_request.yml setstype: Feature.fix(<scope>):andfeat(<scope>):, matching the scopecommitlint.config.cjsalready expects on the commit that closes the issue.Problem,Scope,Acceptance criteriarequired;Prior art in this repoandOut of scopeoptional. No Code of Conduct checkbox, no OS dropdown — those belong on a contributor intake form, not on a roadmap item. The two optional sections are the ones that surfaced duplicates during the backlog triage that prompted this PR.bug,enhancement,documentation,security. Types replace them. What survives is what a bot or a human actually reads:good first issue,dependencies(dependabot),autorelease: *(release-please).The
dependencieslabel was missing on GitHub too, so dependabot dropped it on every PR (#401, #400, #399, #398, #362 all landed unlabelled). It has been created out-of-band; the GitHub label set now matcheslabels.ymlexactly.🧪 How to verify
Then open https://github.com/ai-driven-dev/framework/issues/new/choose: three forms, each stamping a type.
✅ I certify