feat(labels): add common-default labels to canonical seed#88
Merged
Conversation
Expand scripts/labels.mjs with 17 common-default labels on top of the gate-required set #84 already seeded (ci:full, auto-triaged, doc-orphan): - release-note aliases: feature, fix, breaking-change (close categories declared in ArchonVII/.github release.yml that were unseeded) - conventional work types: task, ci, build - GitHub built-in defaults: duplicate, invalid, question, wontfix - contributor onboarding: help wanted, good first issue, contrib-candidate - triage states: needs-info, needs-reproduction, needs-decision, ready New colors use GitHub's canonical default palette where one exists, else reuse an existing seed color; each is sourced in a trailing comment. area:*/platform:* deferred to a future per-repo opt-in. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
ArchonVII
marked this pull request as ready for review
June 17, 2026 14:54
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
1 participant
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.
Closes #87.
What
Expands the canonical label seed (
scripts/labels.mjs) with 17 common-default labels, on top of the gate-required set that #84 already seeded (ci:full,auto-triaged,doc-orphan).feature,fix,breaking-changetask,ci,buildduplicate,invalid,question,wontfixhelp wanted,good first issue,contrib-candidateneeds-info,needs-reproduction,needs-decision,ready37 → 54 labels.
Why
feature/fix/breaking-changeare release-note categories declared inArchonVII/.githubrelease.ymlbut were never seeded — PRs labeled with them (or bots/imported PRs using conventional names) wouldn't group correctly until the label existed in a repo. The rest are the well-known GitHub defaults + standard triage/onboarding labels.Design notes
archon-setup'sapplyLabels.mjsdelegates to this script, so this one change propagates to the wizard; no snapshot to sync.duplicate,invalid,question,wontfix,help wanted,good first issue); otherwise they reuse an existing seed color, cited in a trailing comment per the repo's constants rule. Aliases match their canonical label's color sorelease.ymlgrouping reads consistently.gate-labels.test.mjs) only fails on referenced-but-unseeded; added labels only grow the informational unreferenced list. No gate label was removed.area:*(13),platform:*(3),automated-distribution,managed-baseline—area:/platform:read better as a per-repo opt-in than a uniform block.Verification
npm test→ gate-label audit green; 142 tests pass.node --check scripts/labels.mjsclean.doc-policy-lint.test.mjsfails on local Windows checkouts only — CRLF sensitivity, green in CI; logged separately, pre-existing from feat(lint): add warning-only doc-policy lint #76.)Follow-up (separate PR,
ArchonVII/.github)Wire
labels: ["task"]into.github/ISSUE_TEMPLATE/task.ymlnow thattaskis seeded.