feat: add release-binaries workflow #355
Conversation
| project_path: "./cmd/lassie" | ||
| binary_name: "lassie" |
There was a problem hiding this comment.
Alternatively you can use goreleaser like the one i have set up for index-provider CLI. That also uploads binaries to github releases amongst other stuff; example.
|
is goreleaser superior to this setup? I'm not really fussed as long as it works, I'd love to have consistency across projects but it seems like everyone's having a go at something different with these |
|
I too am not fussed. For me go releaser does more with less config; that's all. Feel free to merge this as is. |
|
fair enough, it is a simpler setup and the name "goreleaser" makes it feel more official... |
| @@ -0,0 +1,26 @@ | |||
| name: GoReleaser | |||
There was a problem hiding this comment.
For goreleaser binary build to do the right thing in this repo a config like this is needed. Once that's added try running goreleaser check to verify the config, and give goreleaser --rm-dist --snapshot a shot to make sure binaries are built as you expect them to (written in dist directory by default).
I also recommend adding dist to .gitingore.
There was a problem hiding this comment.
does more with less config
he said!
ok, added the config and tested it all out
There was a problem hiding this comment.
lol; that's the best kind of true: technically.
rvagg
force-pushed
the
rvagg/release-binaries
branch
from
f162de3
to
44f8ce8
Compare
Closes: #354