Use the right sha in metadata for Update Docker Images action #2090
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
lucacome
requested review from
ciarams87,
soneillf5 and
pleshakov
and removed request for
a team
lucacome
force-pushed
the
chore/update-docker-images-update-sha
branch
from
13ce058
to
bbb1c60
Compare
nginx-bot
force-pushed
the
chore/update-docker-images-update-sha
branch
2 times, most recently
from
fa85338
to
637cb1a
Compare
pleshakov
approved these changes
Oct 14, 2021
nginx-bot
force-pushed
the
chore/update-docker-images-update-sha
branch
from
637cb1a
to
455a704
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 metadata action uses the sha from the context when the workflow is triggered. This is fine for the other workflows where we checkout the code for the same sha.
In this workflow we checkout a different tag and we need the sha from that.