mirror of
https://github.com/glittercowboy/get-shit-done
synced 2026-05-15 03:26:38 +02:00
48b01e4c9f
- docs/agents/issue-tracker.md — GitHub, gsd-build/get-shit-done, .envrc token required
- docs/agents/triage-labels.md — confirmed=AFK-ready, approved-*=human-ready, needs-reproduction=needs-info
- docs/agents/domain.md — single-context, CONTEXT.md sections explained
- CLAUDE.md — fix stale triage label (needs-maintainer-review doesn't exist),
fix stale domain note ('neither exists yet'), add .envrc token reminder to issue tracker summary
1.7 KiB
1.7 KiB
Triage Labels
Maps the five canonical triage roles to the actual label strings in gsd-build/get-shit-done.
| Canonical role | Label in this repo | Notes |
|---|---|---|
needs-triage |
needs-triage |
Auto-applied by GitHub Action on every new issue |
needs-info |
needs-reproduction |
Waiting on reporter — cannot reproduce, more info required |
ready-for-agent |
confirmed |
Bug verified + fully specified — AFK agent can pick up |
ready-for-human |
approved-enhancement / approved-feature |
Enhancement/feature approved by maintainer — human codes it |
wontfix |
wontfix |
Will not be actioned |
Notes on this repo's label model
confirmedis the AFK-agent-ready signal for bugs. It means "verified to exist and reproducible."- For enhancements and features, maintainer approval is
approved-enhancement/approved-featurerespectively. A contributor (human or agent) may not write code until one of these is applied. - There is no separate "ready-for-human" vs "ready-for-agent" distinction for enhancements — both flow through the same
approved-*labels. If the work requires human judgment (design decisions, external access), note it in the issue body. needs-triageis removed when any other state label is applied.needs-reproductionis used instead of the genericneeds-info— be specific in triage comments about what reproduction steps or information are missing.