ci: apply concurrency limit for github workflows #6243
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.
Right now, if we push multiple commits, all our CI workflows pile up in the queue, causing a bit of a jam. We can cut down on this by setting up a concurrency limit. This way, any new workflow that hits the same branch will cancel the previous ones still in queue. But, if we don't want this to happen with our master branch workflows, we can make an exception. Here's how we could set it up:
This setup checks if the workflow is targeting the master branch. If it is, it assigns a unique group name to avoid cancellation. Otherwise, it groups workflows by their name and the branch they're targeting, cancelling any in-progress ones when a new one starts. Let me know if this adjustment is required.
more info: https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#concurrency