Add separate GH Actions root level concurrency group #1299
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
matkoch
force-pushed
the
develop
branch
5 times, most recently
from
0231425
to
d806295
Compare
matkoch
force-pushed
the
develop
branch
3 times, most recently
from
7066bbe
to
985de83
Compare
lahma
force-pushed
the
runner-image-cancel-in-progress
branch
from
892020c
to
4b799cc
Compare
lahma
changed the title
lahma
force-pushed
the
runner-image-cancel-in-progress
branch
2 times, most recently
from
700489f
to
bf7b412
Compare
lahma
changed the title
matkoch
force-pushed
the
develop
branch
4 times, most recently
from
0719711
to
6fe1e3b
Compare
lahma
force-pushed
the
runner-image-cancel-in-progress
branch
from
bf7b412
to
0e5e320
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Different image jobs can be cancelling each others when having same job group definition (it's valid to have it on job level too though). Adding a separate concurrency group to root level will cancel the entire workflow including it's jobs instead of jobs fighting against each other will make the default multi-image setup easier.
I confirm that the pull-request: