#274 additional release logic to try to push manifested releases on publish

[thelamer]

I made a lot of assumption here, realistically If is was you I would have identical logic for commits to master as release tags with publishing workflow.

You can just push to an alternative endpoint like containrrr-dev/watchtower using the git commit as the tag.
The combination of bash commands and goreleaser is a little confusing here, and I still do not understand how the publishing works fully as you have 386 defined in your goreleaser , but there is no tag for it on dockerhub currently. Also there is no logic for the latest tag as far as I can see.

Edit: forgot to mention noticed the blank description for your dockerhub repo, At linuxserver we use a simple node script to keep repo READMEs in sync with dockerhub, totally up to you to keep something like that in there. Reference issue #274

[simskij]

Thanks a bunch, I'm gonna tweak it a bit and take it for a test drive. Hope you dont mind! 😄