Prepare secrets file and upload APK artifact#448
Merged
Conversation
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
2 participants
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.
This pull request updates the GitHub Actions workflow to improve the build process for the project. The main changes involve securely handling secrets required for the build and automating the upload of the generated APK file as an artifact.
Build secrets management:
secrets.propertiesfile using environment variables from GitHub secrets, ensuring that sensitive API keys and credentials are available to the build process without hardcoding them.Build artifact handling:
app/build/outputs/apk/sideload/debug/*.apk) as a build artifact using theactions/upload-artifact@v4action, making it available for download after the workflow completes.