forge.py: merge only when every CI run of the head commit passed #120

Merged
littlefox merged 1 commit from merge-needs-all-runs into main 2026-10-18 17:58:25 +00:00
Owner

PR #116 was merged on a green branch run while its PR packaging run had failed (and main's run after the merge failed too). Both failures were flakes in jobs the change didn't touch (filed as #118 and #119), but the merge should not have happened.

  • pr-merge checks every run of the PR's head commit and refuses while any is running or failed.
  • runs shows the workflow name.

Tested: pr-merge 117 refused while its run was still going.

🤖 Generated with Claude Code

https://claude.ai/code/session_01XJW2ocwLunyaLiUwCBHEP8

PR #116 was merged on a green branch run while its PR packaging run had failed (and main's run after the merge failed too). Both failures were flakes in jobs the change didn't touch (filed as #118 and #119), but the merge should not have happened. - `pr-merge` checks every run of the PR's head commit and refuses while any is running or failed. - `runs` shows the workflow name. Tested: `pr-merge 117` refused while its run was still going. 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_01XJW2ocwLunyaLiUwCBHEP8
forge.py: merge only when every CI run of the PR's head commit passed
All checks were successful
ci / check (push) Successful in 9m0s
ci / desktop (push) Successful in 13m14s
ci / e2e (push) Successful in 16m57s
0e7b8599ce
PR #116 was merged when its branch run (#195) passed, while the PR's
packaging run (#196) failed: the wait looked at one run by number. Now
pr-merge itself checks all runs of the head commit (every workflow, push
and pull_request) and refuses while any is running or failed. 'runs'
shows the workflow too, so two runs of one commit can't be mistaken for
the same thing.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01XJW2ocwLunyaLiUwCBHEP8
littlefox referenced this pull request from a commit 2026-10-19 05:23:03 +00:00
Sign in to join this conversation.
No description provided.