Phase 1: Forgejo Labels (Foundation)
Goal: Standard status and type labels exist on all Forgejo repos, enabling agents to signal workflow state.
Owner: Betty Sue (Forgejo API calls, no repo code)
Repo: N/A — Forgejo API across all repos
Forgejo Issue: N/A (Betty Sue executed directly — no repo code involved)
Labels created:
| Category | Label | Color | Purpose |
|---|---|---|---|
| Status | <code>status:in-progress</code> | #1d76db (blue) | Dev agent is actively working |
| Status | <code>status:qa</code> | #e4a224 (orange) | PR submitted, awaiting QA review |
| Status | <code>status:needs-fix</code> | #d93f0b (red) | QA found issues, back to dev |
| Status | <code>status:approved</code> | #0e8a16 (green) | QA passed, awaiting merge approval |
| Type | <code>type:feature</code> | #5319e7 (purple) | New functionality |
| Type | <code>type:bug</code> | #d93f0b (red) | Bug fix |
| Type | <code>type:devops</code> | #666666 (gray) | Infrastructure/CI/config work |
Deliverables (2026-03-03):
- 7 labels created across 29 Forgejo repos (202 labels created, 1 skipped as pre-existing)
- All repos under
forgejo_admin/now have identical label sets - Labels verified via Forgejo API — all returned HTTP 201
Depends on: Nothing — this was the foundation.