Repository navigation
👷 ci: don't cancel CI runs on main - #27
Merged
Merged
Conversation
Give each push to main its own concurrency group (keyed on the SHA) so every merged commit gets a complete CI record. PRs, tags and releases keep their per-ref groups and still supersede older runs. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Append the SHA only for push events (which only fire on main), so PRs, releases and manual runs keep their exact previous group names with no trailing '-'. Use an explicit folded scalar (>-) so the wrapped expression reads unambiguously as one string. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Not every workflow runs on releases or manual triggers; say "all other events" so the comment stays accurate. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Pushes to
mainshared a single concurrency group per workflow withcancel-in-progress: true, so each merge cancelled the run for the merge before it, leaving gaps inmain's CI history. Settingcancel-in-progress: falsealone wouldn't fix it, because GitHub keeps only one pending run per group and drops the rest.This adds the commit SHA to the group for pushes to
main, so every merged commit gets a complete run. PRs, tags and releases keep their per-ref groups, so a new push to a PR still cancels that PR's older run.Files:
.github/workflows/ci.yml🤖 Generated with Claude Code