chore: created Docker images with version tag#211
Merged
Merged
Conversation
Member
Author
to be honest, me neither, the only way to test would be to change the condition for which to execute so that it'd be executed on a non-main branch, add a "fake" version tag, which would then stay in the history... sadly no really good way to test these kind of things 😕 so I double-checked that this is indeed the correct syntax, and we'll test it on the main branch |
github-project-automation
Bot
moved this from Ready4Review
to Done
in C4DT Engineer's TODO
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
2 participants
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.
build and push Docker images using semantic versioning, for better overview of what is currently deployed