Skip to content

[v3-4-test] Cancel the runs of merged pull requests when they merge (#75683) - #75687

Merged
potiuk merged 1 commit into
v3-4-testfrom
backport-bfb620d-v3-4-test
Oct 26, 2026
Merged

potiuk merged 1 commit into
v3-4-testfrom
backport-bfb620d-v3-4-test

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

The fork CI monitor cancelled them on its 15-minute schedule, so runs of a
merged pull request kept holding runners for up to 15 minutes, and stuck
ones for 30 more before being force-cancelled. Merging pushes to the target
branch, which lets a push-triggered workflow find the merged pull request
directly and cancel its runs right away, without the monitor's search over
every unfinished run.
(cherry picked from commit bfb620d)

Co-authored-by: Jarek Potiuk jarek@potiuk.com
Generated-by: Claude Opus 5

…75683)

The fork CI monitor cancelled them on its 15-minute schedule, so runs of a
merged pull request kept holding runners for up to 15 minutes, and stuck
ones for 30 more before being force-cancelled. Merging pushes to the target
branch, which lets a push-triggered workflow find the merged pull request
directly and cancel its runs right away, without the monitor's search over
every unfinished run.
(cherry picked from commit bfb620d)

Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
Generated-by: Claude Opus 5
@potiuk
potiuk marked this pull request as ready for review October 26, 2026 19:25
@potiuk
potiuk merged commit ee37502 into v3-4-test Oct 26, 2026
30 of 44 checks passed
@potiuk
potiuk deleted the backport-bfb620d-v3-4-test branch October 26, 2026 19:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant