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
Commit b4c5e2c
Browse filesBrowse the repository at this point in the historyBrowse files
fix(server): watch_pull_request wakes once more and stops when the checks finish after a failure
A reported failure could keep the required checks from passing while the
other checks finished, and nothing woke the thread again: no check was newly
failed and the gate could not pass. The watch stayed armed and the thread
stayed in Working until someone noticed.
Once every check has finished and a reported failure still blocks the gate,
the watch now sends one last wake that lists what still fails, and ends, so
the thread returns to the user's inbox. A rerun that goes pending arms the
notice again. The flag rides on the ended watch, so watching again does not
repeat it. An advisory failure after the required checks passed does not end
the watch: the agent already had its completion signal.
Fixes#25497
Co-Authored-By: Claude Fable 5.1 <[email protected]>
Claude-Session: https://claude.ai/code/session_01MrRujdnDgAgch35FAe2w5T
"Watch an open PR for this thread, linking it first if needed. T3 wakes you on failed checks, passed required checks, new comments or reviews, or conflicts. Handle old comments first. Only later ones wake you. After this call, end your turn. The watch stays on after each wake, so do not call this again on a wake. A wake is not a merge decision. Check readiness yourself.",
311
+
"Watch an open PR for this thread, linking it first if needed. T3 wakes you on failed checks, passed required checks, new comments or reviews, or conflicts. Handle old comments first. Only later ones wake you. After this call, end your turn. The watch stays on after each wake, so do not call this again on a wake. Once every check has finished and a reported failure keeps the required ones from passing, T3 wakes you one last time and stops watching; call this again after you push a fix. A wake is not a merge decision. Check readiness yourself.",
commit: input.headSha===null ? "" : ` on ${input.headSha.slice(0,7)}`,
@@ -232,13 +254,18 @@ export function pullRequestWatchMessage(input: {
232
254
"",
233
255
exhausted
234
256
? `T3 Code stopped watching after ${PULL_REQUEST_WATCH_WAKE_LIMIT} comment-only updates in a row. Call watch_pull_request to watch it again.`
235
-
: "Look into each item and act on it as your task requires. This PR stays linked and watched, so do not link, watch, or list it again. End your turn when you are done, and T3 Code wakes you on the next change. When you hand the work back to the user, call unwatch_pull_request first so the thread returns to their inbox.",
257
+
: finished
258
+
? "T3 Code stopped watching: every check has finished and the failures above stand, so no check news can come until the head moves. If you push a fix, call watch_pull_request again. Otherwise hand the work back to the user; the thread is already back in their inbox."
259
+
: "Look into each item and act on it as your task requires. This PR stays linked and watched, so do not link, watch, or list it again. End your turn when you are done, and T3 Code wakes you on the next change. When you hand the work back to the user, call unwatch_pull_request first so the thread returns to their inbox.",
Copy file name to clipboardExpand all lines: docs/user/source-control.md
+3-2Lines changed: 3 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -290,8 +290,9 @@ check fails, the required checks pass, someone else comments or reviews, or the
290
290
conflict. Threads in a project that watch the same pull request share one check. On GitHub, a check
291
291
first asks whether anything changed and reads the pull request only when it did, which keeps
292
292
watching inside GitHub's rate limit. Comments from your own account do not wake it. Watching ends
293
-
when the pull request merges or closes, after 10 wakes in a row that bring only comments, after 8
294
-
failed reads in a row, or when you press Stop on the thread. A rate limit only pauses watching.
293
+
when the pull request merges or closes, when every check has finished and a reported failure keeps
294
+
the required ones from passing, after 10 wakes in a row that bring only comments, after 8 failed
295
+
reads in a row, or when you press Stop on the thread. A rate limit only pauses watching.
295
296
Settling or archiving a thread also ends all its watches. Unsettle the thread before starting a new
296
297
watch. Watching a pull request again does not repeat check or conflict news its last
297
298
watch already reported; unlinking the pull request clears that. Subagents cannot watch pull requests; the thread that delegated to them does. To start or stop
0 commit comments