Add concurrency groups to CI workflows#1065
Open
vharseko wants to merge 2 commits into
Open
Conversation
Add a top-level concurrency group keyed on workflow + ref to every GitHub Actions workflow so redundant runs on the same ref collapse: - build.yml: cancel-in-progress=true, so a new push/PR build cancels the now-superseded in-flight one (the main runner-time saver). - release.yml / deploy.yml: cancel-in-progress=false, so overlapping runs queue instead of aborting an in-flight Maven Central publish, tag push or GitHub release midway.
maximthomas
reviewed
Jul 9, 2026
Co-authored-by: Maxim Thomas <maxim.thomas@gmail.com>
maximthomas
approved these changes
Jul 9, 2026
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
2 participants
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.
Summary
Add a top-level
concurrencygroup (keyed on${{ github.workflow }}-${{ github.ref }}) to the GitHub Actions workflows so redundant runs on the same ref collapse instead of piling up.cancel-in-progressbuild.ymltruedeploy.ymlfalserelease.ymlfalserelease:prepare/release:perform, tag push, GitHub release).Rationale
cancel-in-progress: trueis safe and desirable forbuild.yml: superseded commits don't need their builds finished. Forrelease.ymlanddeploy.ymlit is deliberatelyfalse— cancelling those midway could leave a half-published Maven Central staging repo, a partial GitHub release, or dangling tags, so overlapping runs serialize instead.Notes
codeql.ymlis intentionally not touched here; it lives in a separate open PR (Add CodeQL code scanning workflow #1063) and is not yet onmaster.build.yml, no conflict expected.