Document tea CI-status parsing pitfalls and idle-friendly loop polling #22
Loading…
Reference in a new issue
No description provided.
Delete branch "docs/ci-watch-idle-polling-and-status-parsing"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Two things learned the hard way while babysitting a real PR's CI in a Claude Code session, written up so the next session doesn't re-derive them:
tea pulls <index> --fields ciis not fully authoritative. It has previously dropped a job's row entirely (a PR read all-green while a job had actually failed), and its OSC-8 hyperlink escapes wrap each job's link text — which itself contains a colon (https://…) — so a naive "match after the colon" parser silently grabs the URL instead of the job's status. Documents the escape-stripping needed and recommends cross-checking the commit statuses API (/repos/{owner}/{repo}/commits/<sha>/statuses, grouped by context, newest wins) before calling a PR green.Monitorboth keep a real process running the entire time, which looks identical to active work from the outside. Documents the alternative:/loopin dynamic mode with noMonitorarmed — a single foreground check per iteration, thenScheduleWakeupends the turn with nothing running until the next firing — plus adapting the delay each iteration to what was just observed instead of a fixed cadence.Test plan
docs/Topics/VCS.md) — no code/lint/CI surface in this repo.