Automate building of Docker images into the GitHub registry. #13
Conversation
There are already 3rd party images published on Dockerhub that are wildly out of date. So one automatically up to date official image is probably better than having people rely on unofficial images. - Any push to the `master` branch updates the `:latest` label - Any tag push to `master` will also be labeled with the tag name, so your releases will get stable labels. - Any push to any other branch is labeled with the branch name and the short hash id of the commit.
|
Thanks, this looks great. Sorry I just haven't had a chance to review it yet. |
|
Friendly poke @retzkek , any chance you could take a look at this one? It follows very closely the GitHub provided example code of automatically pushing images and requires no further setup on your part since the necessary authentication tokens are autopopulated by the GitHub state runner. |
If the .git directory is included, the build fails on a new golang feature that naively assumes a build environment with a .git folder has git installed.
|
Sorry @Artanicus I've had a lot going on, and haven't even been farming for a couple months now. If you'd like to take over maintenance I'll put a link to your repo in the README and archive this. |
|
Sure, that works for me. I think there was an option somewhere within repo settings to "transfer" ownership. The core benefit being that it archives the original and leaves URL redirects so that any clones still continue to function. |
There are already 3rd party images published on Dockerhub that are wildly out of date. So one automatically up to date official image is probably better than having people rely on unofficial images.
masterbranch updates the:latestlabelmasterwill also be labeled with the tag name, so your releases will get stable labels.