ci: [WLEO-365] Add Android APK in release artifacts #226
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.
List of Changes
fastlane
init for the Android project;.env.example
with actual values;publish.yml
workflow is now only executed if the release title doesn't containexample
which is the namepublish-app.yml
assigns to the example app release. This avoid running the library publishing workflow when a release for the example is created.Motivation and Context
This PR introduces a workflow which creates an example app release with an Android APK in its assets.
A new GitHub release is created by the aforementioned workflow with
example
in its title.Changelogs are currently not generated as this requires an important refactor on how we tag commits and also on how the library release process is currently handled.
How Has This Been Tested?
This cannot be tested until merged.
Screenshots (if appropriate):
Checklist: