GH Actions: auto-cancel previous jobs for same branch#192
Open
GH Actions: auto-cancel previous jobs for same branch#192
Conversation
When the same branch is pushed again, any still running builds for the same branch should be stopped in favour of starting the build for the newly pushed version of the branch. The `test` workflow did not apply this best practice. Fixed now. Includes minor formatting improvement for the `on` key. Refs: * https://docs.github.com/en/actions/reference/workflows-and-actions/workflow-syntax#concurrency
jrfnl
force-pushed
the
feature/ghactions-fix-concurrency
branch
from
ef10aee to
537c0e6
Compare
Collaborator
Author
|
Sorry for the push noise. Pushed to the wrong branch. |
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.
When the same branch is pushed again, any still running builds for the same branch should be stopped in favour of starting the build for the newly pushed version of the branch.
The
testworkflow did not apply this best practice.Fixed now.
Includes minor formatting improvement for the
onkey.Refs: