chore(ci): use cancel-in-progress to prevent useless CI runs#818
Merged
chore(ci): use cancel-in-progress to prevent useless CI runs#818
Conversation
jansegre
force-pushed
the
chore/ci-cancel-in-progress
branch
from
05f1f23 to
a9ca730
Compare
Member
Author
|
For example, this run was cancelled automatically: https://github.com/HathorNetwork/hathor-core/actions/runs/6563765880/job/17828748211?pr=818 |
glevco
approved these changes
Oct 18, 2023
msbrogli
approved these changes
Oct 18, 2023
2 tasks
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
3 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.
Motivation
Very often we will push a new commit to a PR (recent rebase or otherwise) while the CI is still running and will continue to run wasting CI time and jamming the jobs queue.
Acceptance Criteria
cancel-in-progressconfig to automatically cancel workflow runs when a new one in the same "ref" (branch or tag) starts.Checklist
master, confirm this code is production-ready and can be included in future releases as soon as it gets merged