Repository navigation
docs: route downloads to the release assets - #2
Merged
Merged
Conversation
A binary committed to a repository is served through GitHub's raw file path,
which a phone browser refuses or saves under the wrong name. Release assets
are served as real downloads with the correct MIME type and filename.
The Release workflow builds and attaches the APK for every tag, and GitHub
generates the source zip and tarball automatically, so the Releases page now
carries everything a user needs. Verified against v1.0.0:
discount-hunter-1.0.0.apk HTTP 200, application/vnd.android.package-archive,
attachment; filename=discount-hunter-1.0.0.apk, 2.87 MB
Source code (zip) HTTP 200, application/zip
The downloaded APK was installed on an emulator and launches with no crash.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A binary committed to a repository is served through GitHub's raw file path, which a phone browser refuses or saves under the wrong name. Release assets are served as real downloads.
The Release workflow builds and attaches the APK for every tag, and GitHub generates the source zip and tarball automatically, so the Releases page carries everything.
Verified against v1.0.0: