-
Notifications
You must be signed in to change notification settings - Fork 93
Cancel previous running workflows #427
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
I haven't used it anywhere (just opened a PR to KernelFunctions where we had an open issue about canceling workflows) but I think it could be helpful to configuration in https://github.com/styfle/cancel-workflow-action#advanced-pull-requests-from-forks such that it also works for PRs from forks. |
Could we disable email notification when the workflow is cancelled rather than when it fails? |
.github/workflows/Cancel.yml
Outdated
steps: | ||
- uses: styfle/cancel-workflow-action@0.9.0 | ||
with: | ||
all_but_latest: true |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
By default, only the workflows started before this action are cancelled. This flag cancels all but the latest workflow, which is helpful if the pipeline is saturated
Hmm this seems to have resulted in everything being cancelled because of VersionVigilante failing. |
Oh no I cancelled manually because I didn't want to block other pipelines, sorry! This only runs when merged to master (as per JuliaGaussianProcesses/KernelFunctions.jl#292) |
OK, lets give this a try |
Did not seem to have worked, i.e. this PR still ran two full pipelines: |
I don't know anything about CI, so this might be very wrong - just testing it out
Closes #426