Add 'Publish Docker image' Github Action and enable Dependabot for it. #124
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.
Finally, I gave a stab at #107 using Github Actions. 🎉
Github Action requires
DOCKERHUB_USERNAME
andDOCKERHUB_TOKEN
(generated on DH's security settings page) to be set in the Github secrets section in the repo config.Git pushes will trigger this Github Action to build Docker images and push them to Docker Hub:
branchname
pushessncli:branchname
image tag. Thus,sncli:master
acts as an edge/unreleased/HEAD image tag. Other branches push to their respective image tags (useful for testing feature branches),X.Y.Z
orvX.Y.X
push tosncli:X.Y.Z
,sncli:X.Y
,sncli:X
andsncli:latest
.:latest
tag is the default when pulling if no tag specified, sodocker pull insanum/sncli
pulls latestHEAD
code (assuminginsanum
is your Docker Hub user).Also enabled Dependabot (only for Github Actions manifests). No need to toggle or configure anything.
Also, I've noticed no tag has been pushed since a while ago. Fancy to create a release to test it out? 😉 Not required, thou, as merging will trigger it anyway. Just make sure to set secrets beforehand.