workflow: update build necessity checks for container images #68
Conversation
This file contains hidden or 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
simonbeaudoin0935
requested review from
bjordiscollaku,
keerthi-go and
vishwasudupa
as code owners
Signed-off-by: Simon Beaudoin <[email protected]>
simonbeaudoin0935
force-pushed
the
feature/build-containers-only-when-necessary
branch
from
ce1cefd to
b8e088e
Compare
bjordiscollaku
approved these changes
Nov 12, 2025
simonbeaudoin0935
deleted the
feature/build-containers-only-when-necessary
branch
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.
Do not rebuild+push the container every time a merge is made to main.
When a merge is made and the workflow is triggered on a push:, then examine the diff between before and after the merge to see it the docker/ folder was impacted.
With this, the CI will be lighter