Repository navigation
Cancel superseded builds for each branch and tag - #204
Merged
Merged
Conversation
Signed-off-by: Tim Paine <3105306+timkpaine@users.noreply.github.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
1 participant
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.
Push builds in base CI and the eight Python templates used a unique run ID as their concurrency group, so newer pushes to main or the same tag never canceled running builds. The five JavaScript templates had no concurrency configuration.
Group builds by workflow and full ref with
cancel-in-progress: trueacross base CI and all 13 templates. New runs cancel older runs for the same PR, branch, or tag. Different tags and workflows remain separate.Rendered all 13 templates, checked group isolation, and confirmed triggers and jobs are unchanged. Actionlint passed for all 14 build workflows.