ci: add concurrency groups to workflows #980
Merged
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.
This pull request adds concurrency groups to all existing GitHub Actions workflows.
When a pull request is created, or a commit is pushed to a branch, all workflows related to that event are triggered. However, when subsequent commits are pushed to that pull request/branch, the workflow runs may be delayed until the previous workflow runs complete, due to GitHub's runner concurrency limit.
By adding concurrency groups to the workflows, we can automatically cancel all pending or running workflow runs related to previous commits, allowing workflow runs on newer commits to start faster.
This works by grouping each workflow run by the workflow name and git reference (branch/pull request). When concurrent workflow runs with the same group are queued, this will cause any previous pending or running jobs to be cancelled automatically (
cancel-in-progress: true
).Related: https://docs.github.com/en/actions/using-jobs/using-concurrency