Closed meeDamian closed 4 years ago
Basically do something along the same lines as here: https://github.com/lncm/docker-lnd/blob/master/scripts/new-release.sh
It helps us to never override git tags, and always leaves a trace on the Docker Hub (continues to work identical if someone uses a build-specific, or sha256-specific tags instead).
Done with #31
meeDamian
commented
4 years ago
Basically do something along the same lines as here: https://github.com/lncm/docker-lnd/blob/master/scripts/new-release.sh
It helps us to never override git tags, and always leaves a trace on the Docker Hub (continues to work identical if someone uses a build-specific, or sha256-specific tags instead).