Skip to content

Don't cancel CI runs on main - #304

Merged
bensynapse merged 1 commit into
mainfrom
ci/keep-main-runs
Oct 6, 2026
Merged

bensynapse merged 1 commit into
mainfrom
ci/keep-main-runs

Conversation

@bensynapse

Copy link
Copy Markdown
Owner

When #303 merged a minute after #302, cancel-in-progress cancelled the CI run for #302's merge commit. Its "CI OK" job then failed because its needs were cancelled, so that commit on main showed red. I re-ran it, and it's green now.

The concurrency group is now the commit SHA for pushes, so runs on main never cancel or queue behind each other. Pull requests keep the branch ref as the group, and a new push still cancels the older run. Just turning off cancel-in-progress wouldn't be enough: GitHub still cancels a queued run when a third one arrives in the same group.

Two merges in quick succession cancelled the first one's CI run, which
left that commit on main with cancelled checks and a failed "CI OK". Runs
for pull requests still cancel the older run when a new commit arrives.
@bensynapse
bensynapse merged commit bbe015c into main Oct 6, 2026
12 checks passed
@bensynapse
bensynapse deleted the ci/keep-main-runs branch October 6, 2026 01:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant