Closed kpurdon closed 3 years ago
@cespare anything I can do to help get this reviewed? Thanks!
I'll try to look into this in the next week or two.
@kpurdon @cespare perhaps a GitHub action would make this easier. https://github.com/goreleaser/goreleaser-action
Hey, anything I can do to help move this along? Adding prebuilt binaries would easy adoption on my team.
As @benatkin suggested, I opened https://github.com/cespare/reflex/pull/80 providing published artifacts from a GitHub action. It should Just Work.
This PR adds support for the minimum needed goreleaser config to generate releases with binaries. This resolves #31 and is an alternative to #67.
An example on my fork of a release is: https://github.com/kpurdon/reflex/releases/tag/v0.2.1
This can currently be run by doing the following:
GITHUB_TOKEN="a_repo_scope_github_token"
is set.goreleaser
.This is more or less from the example here: https://goreleaser.com/quick-start/.
I avoided adding any automation (TravisCI, Github Actions, ...) since that would be difficult for me to test, but those things are supported:
The process for this would be to merge, tag a new release, and run goreleaser (following my steps above) to create a new release with binaries.