You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Armed PR sweep: a red or conflicted auto-merge PR wakes its owning thread within 10 minutes #880
What: an "armed PR sweep" inside T3. T3 itself lists every open PR that has auto-merge on, judges it (red, conflicted, auto-merge turned off, closed, stalled) and wakes the top-level thread that owns it (found from T3's own PR links, up the parent chain; a project fallback thread otherwise). Nothing has to be registered, so nothing can be forgotten.
Why the owner wants it: red or conflicted PRs that were armed sat for hours because the only signal was a PR comment nobody read. Goal: a red or conflicted armed PR wakes the right thread within 10 minutes.
Already built: the merge queue's notify command on armed PRs it passes over #674 (#129), one automatic re-run for known infrastructure failures #707 (#130). Owner questions #160-#162 answered.
Left (checklist):
1 armed.* settings and a pure judge with table tests
2 Sweep service in dry mode (logs and wait_list rows, sends nothing)
3 Delivery: send once, joined message, hand over to the fallback thread, cap per PR head
4 Settings UI, wait_list rows for armed PRs, docs
6 A small pressure-note fork-ci action (machine pressure numbers as an annotation on a failed run)
Project side: each project turns on the re-run action and drops its own "watch the head" telling
Related:#852 (one wake-up mechanism) and #848 (one merge path). This sweep should feed those, not add a third system.
Done when: a red or conflicted armed PR wakes its owning thread within 10 minutes, exactly once per head, with no project setup.
One more piece carried over from a consumer project (its armed-PR wake-ups now wait on this issue): besides waking the owner, list armed PRs that have not been green for 30+ minutes in one place (a status view, wait_list rows or a daily report) with PR, head, the failing check or "conflict", and since when. On one day seven armed PRs sat red or conflicted for 4-8 hours unseen; a conflicted PR gets no CI runs, so it never goes green by itself.
Activity
scuttletoby commentedon Nov 22, 2026
One more piece carried over from a consumer project (its armed-PR wake-ups now wait on this issue): besides waking the owner, list armed PRs that have not been green for 30+ minutes in one place (a status view,
wait_listrows or a daily report) with PR, head, the failing check or "conflict", and since when. On one day seven armed PRs sat red or conflicted for 4-8 hours unseen; a conflicted PR gets no CI runs, so it never goes green by itself.🤖 Generated with Claude Code