docs: an epic's children are linked as dependencies, not labelled

This commit is contained in:
sam committed 2026-11-13 13:54:28 +11:00
1 parent 757c3016ae
commit 6d54952cbb
1 file changed
+5 -2
+5 -2
View File
@@ -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/<slug> --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/<slug>` 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/<slug>` 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.