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 ecfe56d
Browse filesBrowse the repository at this point in the historyBrowse files
pr-wait.py: wait for finished checks to settle before reporting (#31)
Right after a pull request is opened, GitHub can show only an earlier
push run, already finished, before it adds the pull request's own run;
pr-wait.py then reported "passed" too early. The result now counts only
once the same finished checks have been seen for --settle seconds
(default 30).
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Copy file name to clipboardExpand all lines: README.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -113,7 +113,7 @@ Waits until every check on a pull request has finished, then exits with a status
113
113
| 5 | No check appeared on the latest commit within `--first-check-wait` (default 3 minutes) |
114
114
| 6 |`gh` is not installed, or failed five times in a row (not logged in, no such pull request, no network) |
115
115
116
-
It asks GitHub every `--interval` seconds (default 30). Progress lines carry the time in UTC.
116
+
It asks GitHub every `--interval` seconds (default 30). A result counts only once the same finished checks have been seen for `--settle` seconds (default 30), because GitHub can add a run a few seconds late, such as a pull request's own run after an earlier push run has already finished. Progress lines carry the time in UTC.
117
117
118
118
### Testing extensions and styles: `phpbb-test-board/`
0 commit comments