Use 'concurrency' in GitHub workflows #3610
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.
Use concurrency in GitHub workflows to cancel in-progress or pending runs for the same ref.
This automatically cancels builds if a newer commit is pushed to a branch or pull request.
Documentation: https://docs.github.com/en/actions/using-jobs/using-concurrency
Similar settings exist for AppVeyor and Drone CI but cannot be enabled from the configuration file.
AppVeyor
AppVeyor calls this feature Rolling builds. It can be enabled in the general project settings:
Drone CI
Drone CI has 3 CLI settings that control this functionality:
https://docs.drone.io/cli/repo/drone-repo-update/