From 6d54952cbbe840dfeb7db0d156a52897150112ac Mon Sep 17 00:00:00 2001 From: Sam Catlow Date: Fri, 13 Nov 2026 13:54:28 +1100 Subject: [PATCH] docs: an epic's children are linked as dependencies, not labelled --- CLAUDE.md | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/CLAUDE.md b/CLAUDE.md index 93d9799c4..e43c2fd78 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -207,7 +207,6 @@ GitHub is a read-only mirror; do not open, close or comment there. ```bash tea issues list -r sam/archie --state open --labels critical -tea issues list -r sam/archie --labels epic/ --state open tea issues view 497 tea issues edit 497 --add-labels in-progress --add-assignees sam tea comment 497 "what changed, and what was run" @@ -218,7 +217,11 @@ tea issues close 497 Keep it to that. - Labels carry state: a type (`bug`, `feature`, `task`, `chore`, `epic`, `decision`, `discovery`), a priority (`critical`, `high`, `medium`, `low`), `in-progress` - and `deferred`. Open/closed is the issue state, not a label. `epic/` says which epic an issue belongs to. + and `deferred`. Open/closed is the issue state, not a label. +- An epic's children are its dependencies: link each one as it is filed (Gitea + MCP `issue_write` `add_dependency`, the epic `blocked_by` the child), plus any + real blocker between children. No `epic/` label; the dependencies are + the link, and the only place the web UI shows an epic's children. - `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.