gha: Skip duplicate image build on merge #581
Merged
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
|
Workflow examples for the duplicate build:
|
BbolroC
changed the title
BbolroC
changed the title
mkulke
reviewed
Nov 15, 2024
BbolroC
force-pushed
the
skip-duplicated-image-build-on-merge
branch
from
6213757 to
08fcfad
Compare
mkulke
approved these changes
Nov 15, 2024
The following workflows are triggered twice during a merge: - build-kbs-image.yml - build-as-image.yml For self-hosted runners, which often have a limited number of available runners, this duplicate build is unnecessary and may cause CI bottlenecks. This commit ensures the workflow of interest is skipped when `github.event_name` is `push`', which occurs during a merge. Signed-off-by: Hyounggyu Choi <[email protected]>
BbolroC
force-pushed
the
skip-duplicated-image-build-on-merge
branch
from
08fcfad to
75eb9f7
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.
The following workflows are triggered twice during a merge:
For self-hosted runners, which often have a limited number of available runners, this duplicate build is unnecessary and may cause CI bottlenecks.
This PR ensures the workflow of interest is skipped when
github.event_nameispush, which occurs during a merge.Signed-off-by: Hyounggyu Choi [email protected]