TESTING -- ci: cancel previous workflows when branch is updated #5
Conversation
This file contains 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
When commits are pushed to a branch, the CI workflow is triggered. However in most cases (development branches, pull requests) we don't want previous jobs to keep running; it is just wasteful of resources. Therefore add a special workflow to deal with the situation [1]. An exception is made for pushes to the master branch, otherwise nothing might get build for a long time if many updates are made back-to-back. Link: [1] https://github.com/marketplace/actions/cancel-workflow-action#advanced-pull-requests-from-forks Signed-off-by: Jerome Forissier <jerome.forissier@linaro.org>
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.
When commits are pushed to a branch, the CI workflow is triggered.
However in most cases (development branches, pull requests) we don't
want previous jobs to keep running; it is just wasteful of resources.
Therefore add a special workflow to deal with the situation [1].
An exception is made for pushes to the master branch, otherwise nothing
might get build for a long time if many updates are made back-to-back.
Link: [1] https://github.com/marketplace/actions/cancel-workflow-action#advanced-pull-requests-from-forks
Signed-off-by: Jerome Forissier jerome.forissier@linaro.org