Queued cancel action can't cancel others

[thomwiggers]

I added this action to my workflows, but I have a lot of them. Then I realised an important limitation of this tool: if your pipeline is saturated, this action won't be scheduled. This means that the behaviour is a bit different from what you might get on, e.g., Travis CI, where the scheduler terminates stale workflows, thus clearing a saturated pipeline for CI to immediately start working on the new commit.

It may be helpful to document this limitation.

[thomwiggers]

Would it make sense to add a feature where a run cancels all but the latest workflow, including itself? That would alleviate this issue a bit.

[styfle]

Try the Advanced Usage where cancel is handled in a single workflow so it can cancel other workflows.

This allows you to cancel queued workflows.

[thomwiggers]

I have too many workflows and they are partially generated automatically, so that is not feasible for me. My queue can be hundreds of jobs, so the "cancel these workflows" task would still be postponed for hours, while I want (as implemented in #35) other workflows to cancel themselves and all-but-the-last one.

[RhinosF1]

This is a slight issue for us too. Allowing cancel self would be good.

we have in excess of 80 jobs per commit on average so a few commits going at once can easily send it high.

[styfle]

Fixed in #35 with a new all_but_latest flag.