ci: interim labels-bootstrap dispatch — the taxonomy as a job, not a paste #22
No reviewers
Labels
No labels
attention
blocked
blocker:ci-red
blocker:conflict
blocker:drill-pending
blocker:unrequested
bug
claimed
documentation
enhancement
epic
merge-next
needs-ruling
needs-triage
offsite
post-merge
ready
release
scope:docs
scope:guards
scope:labels
scope:release-flow
stale
state:addressing
state:bots-reviewing
state:building
state:needs-human
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: heavy-duty/ceremony#22
Loading…
Reference in a new issue
No description provided.
Delete branch "ci/labels-bootstrap"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Answers the obvious question ('why didn't we just do a job for that, like rig/box/cast?') with the job. Label definitions need write; the agents team is triage on purpose — so the taxonomy converges through the repo's own Actions token, the family's exact pattern.
workflow_dispatchonly;permissions: issues: write; every row an upsert (--force), so one click converges names, colors and the descriptions the wrapped paste ate.blocker:drill-pendingrow the family lore says bots can't mint — the Actions token can.After merging: Actions → labels-bootstrap → Run workflow (the dispatch click needs write — that's you).
🤖 Generated with Claude Code