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
It seems wasteful and somewhat confusing to me to keep release archives (tarballs) in the releases directory in the repo itself.
releases
The most obvious solution is to create GitHub releases with the proper tags and attaching the actual archives as binaries to each GitHub release.
The text was updated successfully, but these errors were encountered:
All tags and tarballs/md5s have been added to tags now, and #48 was merged, so closing this.
Sorry, something went wrong.
No branches or pull requests
It seems wasteful and somewhat confusing to me to keep release archives (tarballs) in the
releases
directory in the repo itself.The most obvious solution is to create GitHub releases with the proper tags and attaching the actual archives as binaries to each GitHub release.
The text was updated successfully, but these errors were encountered: