Compare commits

..
1 Commits
Author SHA1 Message Date
archvillainetteandClaude Opus 5 f958436238 docs(agents): warn that tea label edits are not visible to an immediate read-back
ci / ci (pull_request) Successful in 4m10s
`tea issues edit --add-labels` applies org-level labels correctly, but
`tea issues ls` can return the pre-edit label set for several seconds
afterwards. Reading that stale result as a failed edit sent one
investigation down three wrong paths (missing token, tea too old, switch
to curl) before the original command turned out to have worked.

Recorded next to the existing `</dev/null` trap; both are tea behaviours
that read as breakage to a non-interactive caller.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-08-05 12:53:46 +02:00
-14
View File
@@ -59,20 +59,6 @@ preference — move it.
`tea pr create`. `tea pr create`.
- **Apply / remove labels**: `tea api --method PATCH` on the issue, or - **Apply / remove labels**: `tea api --method PATCH` on the issue, or
`tea api repos/ShadowsOverWestgate/sow-tools/issues/<number>/labels` endpoints. `tea api repos/ShadowsOverWestgate/sow-tools/issues/<number>/labels` endpoints.
- **Org-level labels (`Kind/*`, `Priority/*`, `Reviewed/*`, `Status/*`)**: `tea
issues edit --add-labels` / `--remove-labels` do **not** apply these on tea
0.14.0, the version nixpkgs pins. Name resolution searches only this repo's
own label set, so an org label matches nothing and the command exits 0,
prints the issue, and changes nothing — no error, no warning. Repo-local
labels (`wayfinder:*`, `ready-for-agent`) are unaffected. PRs no-op the same
way. Upstream fixed it in v0.15 (`modules/task/labels.go` now also queries
`ListOrgLabels`), so this expires when tea is bumped; until then apply org
labels in the web UI. Note `tea labels` lists repo labels only, so it will
not show you the org set either — `tea api orgs/ShadowsOverWestgate/labels`
does.
- **Verify every label change by re-reading it.** `tea issues ls -o json` has a
`labels` field; use it. A label command exiting 0 is not evidence it applied,
and assuming otherwise has already cost one investigation several wrong turns.
`tea issues edit --add-labels` works too, org-level labels (`Kind/*`, `tea issues edit --add-labels` works too, org-level labels (`Kind/*`,
`Priority/*`) included, but a read-back straight afterwards can still show `Priority/*`) included, but a read-back straight afterwards can still show
the old set — `tea issues ls` has returned stale labels for several seconds the old set — `tea issues ls` has returned stale labels for several seconds