feat: snooze threads when their pull request watch comes back green by flamboh · Pull Request #4 · flamboh/t3code

flamboh · 2026-09-22T23:19:52Z

Note

🤖 Claude Opus 5.5 on behalf of Oliver

Stacked on #3.

ELI5

If you want, T3 Code can tuck a thread away once its pull request's CI comes back all green, and bring it back if a check later fails or someone leaves review feedback.

Why

A thread whose PR is green usually needs nothing until review. It still sits in the inbox until you snooze it by hand.

Implementation

New server setting snoozeGreenPullRequests: off (default), "indefinitely", or a number of hours. Settings → General → Organization on web, Threads settings on mobile. Gated on a new pullRequestWatchAutoSnooze capability.
A watch delivery is green when checks_finished is the only hit and every check passed or skipped. A green delivery arms a row in pull_request_auto_snoozes (migration 058).
The row waits for the agent's reply to that notification to finish, then dispatches thread.snooze. A failed reply, a pending approval, a pin, or a snooze the user already set drops it instead.
While snoozed, a slow check (every 15 min) reads the PR through the existing watch observer. A new failed check or new review remark dispatches thread.unsnooze (new pull-request reason). Merge/close, a timer wake, a manual unsnooze, or new agent activity retire the row without waking anything.
"Indefinitely" is a far-future wake time (INDEFINITE_SNOOZE_UNTIL), so the snooze model needs no new wake state. Plain open-ended snoozes show ∞ instead of a countdown.
The thread carries an optional pullRequestSnooze (PR, wokeAt, wakeReasons) in its JSON payload, so no projection migration. Auto-snooze sets it, a pull-request unsnooze records why it woke, and any manual snooze, wake, pin, or new message clears it.
Visibility: a watched snoozed row shows a blue closed eye ("Watching feat: Commit, Push and Create PR actions pingdotgg/t3code#13 · wakes on a failed check or review"). A PR wake reuses the existing Woke pill with an open-eye icon, an amber ring on the row, and a tooltip saying what happened. The thread banner says "New review feedback on feat: Commit, Push and Create PR actions pingdotgg/t3code#13" with a View pull request action. Mobile rows get the same eye icons and ring.

Why poll instead of webhooks

T3 servers usually run on a laptop behind NAT, and GitHub webhooks need a public URL plus admin access to each repo. The observer already exists and works anywhere gh does. One read per snoozed PR every 15 minutes is small next to the one-minute watch poll.