Skip to content

Conversation

@adombeck
Copy link
Contributor

The CI jobs run for a long time and use a lot of resources. If commits are pushed to the same PR in quick succession, the CI jobs run multiple times in parallel, even though older runs are usually not needed. This change saves some resources by automatically cancelling in-progress workflows on new pushes to the same branch.

The implementation is directly from the example of the concurrency keyword: https://docs.github.com/en/actions/reference/workflows-and-actions/workflow-syntax#example-using-concurrency-and-the-default-behavior

The CI jobs run for a long time and use a lot of resources. If commits
are pushed to the same PR in quick succession, the CI jobs run multiple
times in parallel, even though older runs are usually not needed. This
change saves some resources by automatically cancelling in-progress
workflows on new pushes to the same branch.

The implementation is directly from the example of the concurrency keyword:
https://docs.github.com/en/actions/reference/workflows-and-actions/workflow-syntax#example-using-concurrency-and-the-default-behavior
@adombeck adombeck requested a review from a team as a code owner November 11, 2025 16:26
@adombeck adombeck merged commit db84761 into main Nov 11, 2025
17 checks passed
@adombeck adombeck deleted the cancel-in-progress branch November 11, 2025 18:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants