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
..
book.yml	Use the native concurrency property to cancel workflows (#4572)	2023-08-14 03:16:03 +00:00
docker-antithesis.yml	Use the native concurrency property to cancel workflows (#4572)	2023-08-14 03:16:03 +00:00
docker.yml	Use the native concurrency property to cancel workflows (#4572)	2023-08-14 03:16:03 +00:00
linkcheck.yml	Use the native concurrency property to cancel workflows (#4572)	2023-08-14 03:16:03 +00:00
local-testnet.yml	Use the native concurrency property to cancel workflows (#4572)	2023-08-14 03:16:03 +00:00
release.yml	Use the native concurrency property to cancel workflows (#4572)	2023-08-14 03:16:03 +00:00
test-suite.yml	Use the native concurrency property to cancel workflows (#4572)	2023-08-14 03:16:03 +00:00