From 27df64f8b008ea2d7f1a5d6cd8a7d12be48d4a41 Mon Sep 17 00:00:00 2001 From: Sam Catlow Date: Fri, 13 Nov 2026 02:55:10 +1100 Subject: [PATCH] docs(agents): use the in-progress and deferred labels --- CLAUDE.md | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/CLAUDE.md b/CLAUDE.md index 170f865e8..6170dc285 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -190,7 +190,7 @@ GitHub is a read-only mirror; do not open, close or comment there. tea issues list -r sam/archie --state open --labels p0 tea issues list -r sam/archie --labels epic/ --state open tea issues view 497 -tea issues edit 497 --add-labels status::in_progress --add-assignees sam +tea issues edit 497 --add-labels in-progress --add-assignees sam tea comment 497 "what changed, and what was run" tea issues close 497 ``` @@ -198,9 +198,8 @@ tea issues close 497 - An issue is the plan: what is wrong or wanted, and how you know it is done. Keep it to that. - Labels carry state: a type (`bug`, `feature`, `task`, `chore`, `epic`, - `decision`, `discovery`), a priority (`p0` highest to `p3`), - `status::in_progress` and `status::deferred`. Open/closed is the issue state, - not a label. `epic/` says which epic an issue belongs to. + `decision`, `discovery`), a priority (`p0` highest to `p3`), `in-progress` + and `deferred`. Open/closed is the issue state, not a label. `epic/` says which epic an issue belongs to. - `tea` drops labels on `issues create` and `edit --add-labels`. Label through the Gitea MCP connector, by label ID: it resolves names from the first 50 labels only.