We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
My Go projects are only consumed via Docker images, so I have no need to attach the archives/binaries to the release.
We use GitLab internally and release frequently, these releases cumulatively use significant disk space for no gain.
I'd like to configure the release to upload no archives/binaries.
Create an archive containing no data, so the release only uploads that empty archive, to reduce disk usage.
Discussion #3268
The text was updated successfully, but these errors were encountered:
PR already opened in #3282
Sorry, something went wrong.
Wow thanks, I'd have happily contributed!
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
caarlos0
Successfully merging a pull request may close this issue.
Is your feature request related to a problem? Please describe.
My Go projects are only consumed via Docker images, so I have no need to attach the archives/binaries to the release.
We use GitLab internally and release frequently, these releases cumulatively use significant disk space for no gain.
Describe the solution you'd like
I'd like to configure the release to upload no archives/binaries.
Describe alternatives you've considered
Create an archive containing no data, so the release only uploads that empty archive, to reduce disk usage.
Search
Code of Conduct
Additional context
Discussion #3268
The text was updated successfully, but these errors were encountered: