Publish to DockerHub when a new tag is created #463
Merged
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
The publish to DockerHub appears to have been broken for a while now. This attempts to address the issue by adding a new GitHub action to handle pushing to DockerHub if the current ref is a tag. This did involve some changes to the Dockerfile. I've tested the result and updated the `docker_test` target accordingly.
pseudomuto
force-pushed
the
push_to_docker_on_tag
branch
from
c3820bc to
16c28d2
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 publish to DockerHub appears to have been broken for a while now. This attempts to address the issue by adding a new GitHub action to handle pushing to DockerHub if the current ref is a tag.
This did involve some changes to the Dockerfile. I've tested the result and updated the
docker_testtarget accordingly.