GHA build to replace (unused) CircleCI #52
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
GHA to build debug APK on branches/main and upload signed artifacts to a release when creating a release in GHA. Version number management remains manual. The release upload can't really be tested without running a release so we'll tag a v3.0.8 after merging this to check all's well.
microbit-matt-hillsdon
force-pushed
the
gha-build
branch
from
1884bf2 to
22001cc
Compare
microbit-matt-hillsdon
changed the title
|
I think we should probably split release and build into their own yml files so they can be triggered separately and don't need to use "if". That way we'll lose the "skipped" part. |
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.
GHA to build debug APK on branches/main and upload signed artifacts to a release when creating a release in GHA. Version number management remains manual.
The release upload can't really be tested without running a release so we'll tag a v3.0.8 after merging this to check all's well. That and all future releases should be created via the GH releases UI creating the corresponding tag that way too.