Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Build artifacts shouldn't be committed #23

Open
grawlinson opened this issue May 13, 2021 · 3 comments
Open

Build artifacts shouldn't be committed #23

grawlinson opened this issue May 13, 2021 · 3 comments
Labels
enhancement New feature or request

Comments

@grawlinson
Copy link

I think if Goreleaser is automatically attaching the binaries (a.k.a. artifacts) to the git release/tags, there is no need for binaries to be committed directly to the repository.

Applies to files in dist/ and ghosts in the repository root.

@StevenBlack
Copy link
Owner

Thanks George @grawlinson this is a good point.

Question for you: how would I distribute binaries for folks who don't have a Go build environment?

(Sorry for the looooong delay in replying. I missed the notification)

@grawlinson
Copy link
Author

Goreleaser has documentation and an example repository that makes use of GitHub Actions to create binaries using GitHub's free CI/CD and attaches them to tags as seen here.

Users can then navigate to the most recent tag and download the required binaries.

Am I understanding your question right?

@StevenBlack
Copy link
Owner

Yes George @grawlinson great answer. I'll do that!

@StevenBlack StevenBlack added the enhancement New feature or request label Oct 15, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants