From f958436238c0395ac65306a3160cd542c589454b Mon Sep 17 00:00:00 2001 From: vickydotbat Date: Wed, 5 Aug 2026 12:53:46 +0200 Subject: [PATCH] docs(agents): warn that tea label edits are not visible to an immediate read-back `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 ` --- docs/agents/issue-tracker.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/docs/agents/issue-tracker.md b/docs/agents/issue-tracker.md index 6c15f20..878bb7a 100644 --- a/docs/agents/issue-tracker.md +++ b/docs/agents/issue-tracker.md @@ -59,6 +59,12 @@ preference — move it. `tea pr create`. - **Apply / remove labels**: `tea api --method PATCH` on the issue, or `tea api repos/ShadowsOverWestgate/sow-tools/issues//labels` endpoints. + `tea issues edit --add-labels` works too, org-level labels (`Kind/*`, + `Priority/*`) included, but a read-back straight afterwards can still show + the old set — `tea issues ls` has returned stale labels for several seconds + after an edit that succeeded. Never conclude an edit failed from a single + immediate list; re-read after a pause, or use the `labels` endpoints above, + whose response *is* the resulting label set and needs no second call. - **Close**: `tea issues close ` `tea` infers the repo from the git remote when run inside the clone.