GitHub actions builds of CI builds

[GhettiGuru]

I messed with automation building CI builds using dev branch island and Deagle if you want to use for automated ci builds in GitHub actions. Lol wasn't easy, I didn't realize manifest merge errors at first were caused by the different build flavors, in the end I tooled the workflow to only build normal complete debug flavor, and things went my way finally. Just workflow yaml and a few edits to gradle config in the end are all that's needed. For signing the compiled apks, I took my jks signing key (bks bouncy castle or pks12 any format signature keystore will work the same) and base64 -w 0 my_key.jks > keystore.txt , then copied the encrypted code in the output txt and stored it as a GitHub secret with tag KEYSTORE_BASE64 , then the alias and password for key are all also stored as secrets in fields labeled KEY_ALIAS , KEYSTORE_PASSWORD , and KEY_PASSWORD . I have workflow set to decode the base64 key and sign the compiled apks, I used my usual v1 and v3 only signing scheme but this can be edited in build.gradle in /assembly . Feel free to use or not, could definitely make automated builds easier