docs(agents): use the in-progress and deferred labels
This commit is contained in:
1 file changed
+3
-4
@@ -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/<slug> --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/<slug>` 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/<slug>` 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.
|
||||
|
||||
Reference in new issue
Block a user