feat: goreleaser init#24
Conversation
|
@decentral1se ah, I also just looked at that :) a feature I'm missing about goreleaser is that it doesn't actually create a Changelog file, it just adds the changes to the github release, right? If this repo is ever moved to somewhere else the changelog/release notes will be lost. |
|
Oh shit, that's true! That kind of sucks yeh... Maybe doing it manually is the way? https://stackoverflow.com/a/57760234 Feel free to close if you want to take it in another direction ✌️ |
|
@decentral1se hmm, lets see, maybe we find an alternative, or as you said do it by hand. For the first release most commits don't adhere to conventional commits anyway. https://github.com/commitizen-tools/commitizen seems to mostly do what we want as well, I'll play around with it for a bit |
#16
This is just a start.
I used:
I think you need to make a tag and then you start to run the relevant release commands. Source:
E.g.
goreleaser release --snapshot --cleanI leave it to you @goapunk as I imagine you might want to integrate it into Github?