Steven
Steven
The `workflow_id` should be another workflow id (or workflow name), not itself. See the [README.md](https://github.com/styfle/cancel-workflow-action/blob/main/README.md) for example usage.
That feature was added in https://github.com/styfle/cancel-workflow-action/pull/55 and looks like its untested. You could try using this example instead: https://github.com/vercel/next.js/blob/canary/.github/workflows/cancel.yml
I think `pull_request_target` is necessary for forks if I remember correctly
Very cool! Looks like its still in beta and subject to change though. https://docs.github.com/en/actions/reference/workflow-syntax-for-github-actions#concurrency
Also mentioned here https://github.com/styfle/cancel-workflow-action/issues/133#issuecomment-1040039549
> If I really need two runs not to overlap What's the use case here? Doesn't sound like typical CI testing?
I think another Action is a good workaround, it keeps this Cancel Action simple 😄 I'll keep this issue open if others want to upvote, then we can revisit if...
Thanks for the PR! If this gets a few upvotes and others want it, we can merge it. I'll review soon 👍
Indeed, the branch is necessary https://github.com/styfle/cancel-workflow-action/blob/ad6cb1b847ffb509a69b745b6ee2f1d14dfe14b8/src/index.ts#L22-L30 We might be able to add an option for `ignore_branch: true` to only use the SHA 🤔
Great! Do you want to submit a PR?