lighthouse/.github
Jimmy Chen ca050053bf Use the native concurrency property to cancel workflows (#4572)
I noticed that some of our workflows aren't getting cancelled when a new one has been triggered, so we ended up having a long queue in our CI when multiple changes are triggered in a short period.

Looking at the comment here, I noticed the list of workflow IDs are outdated and no longer exist, and some new ones are missing:
dfcb3363c7/.github/workflows/cancel-previous-runs.yml (L12-L13)

I attempted to update these, and came across this comment on the [`cancel-workflow-action`](https://github.com/styfle/cancel-workflow-action) repo:
> You probably don't need to install this custom action.
>
> Instead, use the native [concurrency](https://github.blog/changelog/2021-04-19-github-actions-limit-workflow-run-or-job-concurrency/) property to cancel workflows, for example:

So I thought instead of updating the workflow and maintaining the workflow IDs, perhaps we can try experimenting the [native `concurrency` property](https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#concurrency).
2023-08-14 03:16:03 +00:00
..
custom Enable proposer boost re-orging (#2860) 2022-12-13 09:57:26 +00:00
workflows Use the native concurrency property to cancel workflows (#4572) 2023-08-14 03:16:03 +00:00
ISSUE_TEMPLATE.md Remove links to old master branch (#2190) 2021-02-11 06:06:54 +00:00
PULL_REQUEST_TEMPLATE.md Add PR and issue templates 2018-10-14 14:51:59 +11:00