feature/use-latest-docker-tag#154
Merged
Merged
Conversation
Signed-off-by: DBT pre-commit check
chopkinsmade
force-pushed
the
feature/use-latest-docker-tag
branch
from
3b3c9f7 to
c76221e
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
What
Always run the secret scan using the :latest docker image
Why
As part of the release process, the :latest docker tag is updated with the latest version. We can use this inside the hook, instead of calculating the current version
How this has been tested
Reviewer Checklist