chore(workflows): add ability to cancel all but latest workflow run #5637
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.
Description
Previously, only workflows older then the current workflow were canceled
In very deep queues this means the current instance may not even run until there are future
runs enqueued, and those will not run - and thus will not cancel - the current run, leaving
the queue in a clogged state
Now any time a run instance finally gets off the queue and runs it will check all runs -
including runs queued after the current one - and it will clear all non-current runs including
itself, hopefully unclogging the queue
styfle/cancel-workflow-action#62 is the upstream PR
In the process I removed the github_token as in current versions of the action it is optional, and the one that was specified here is now the default.
Related Issues
No related issue logged, but @Salakar and @rrousselGit mentioned it was hurting productivity and requested I take a look
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes (
[x]
).This will ensure a smooth and quick review process. Updating the
pubspec.yaml
and changelogs is not required.///
).melos run analyze
) does not report any problems on my PR.Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?