Stop post-merge CI on main cancelling itself #1076
No reviewers
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
jaylouisw/packetforge!1076
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "ci/push-runs-not-cancelled"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The concurrency group fell back to
github.reffor anything that was not a pull request — and for every push tomain,github.refis the same string. So every merged PR joined one shared group, and the moment merges became quick they started cancelling each other.Measured minutes after the runner's capacity went 1 → 2:
Four merges, four verification runs, three of them dead before starting.
mainwas only ever verified when nothing else was happening — which on a busy queue is never. This is the same shape as the scheduled-workflow deadlock in #1071, and it is the other half of why "main is unverified on merge" kept being true even after #1072 made the matrix dispatchable.github.shakeeps the original intent and removes the collision:One line, no change to what any job does.
jaylouisw referenced this pull request2026-11-08 15:23:18 +00:00