Update the 0.1.0 image in addition to the release for each merged commit in main #371
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
…mit in main Signed-off-by: Jose R. Gonzalez <[email protected]>
jsm84
approved these changes
Jul 10, 2023
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.
There's a 0.1.0 tag at quay.io/redhat-certification/chart-verifier:0.1.0, but it's pointing to an older release. I couldn't find any automation that's updating that image.
This PR adds logic to build and push the 0.1.0 image tag on each merged commit, just like we do releases. We use the same "build" logic that's used in the "Build, Test, Release" workflow to keep things consistent. This may change later, but as that's more of a sweeping change, I figured it best to change as little as possible for the moment.