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.
The following commits are intended to make this repository fork-friendly by refactoring the workflows of GitHub Actions.
This CI setup allows to create a Molly release every time a new tag is pushed to the repository. To trigger a final build, push the tag to the
main
branch. To trigger a pre-release build, push to any other branch. Tags can be lightweight or annotated, although the latter are preferred for stable releases.A draft containing the built APKs will be created in GitHub Releases after running the workflow. Once the draft is reviewed and published, the APKs are recompiled and reproducible builds are tested automatically.
The build configuration is read from
app/gradle.properties
and overridden by eitherreproducible-builds/ci/release.env
orreproducible-builds/ci/prerelease.env
.Pre-releases have different app name ("Molly Insider") and package ID so they can be installed side-by-side with final releases.
To optionally sign the APKs, store the KeyStore into GitHub Secrets:
RELEASE_KEYSTORE
containing the KeyStore file encoded in base64, key alias:release
RELEASE_KEYSTORE_PASSWORD
with the passwordTEST_KEYSTORE
containing the KeyStore file encoded in base64, key alias:test
TEST_KEYSTORE_PASSWORD
with the passwordTo use your own Google Maps API Key create a secret
MAPS_API_KEY
.If the
PUBLISH_PAT
secret exists, it takes preference overGITHUB_TOKEN
. This is useful in case the default token has read-only permissions.