Add GitHub actions workflow to test-build pull request branches #316
+84
−0
Conversation
This file contains 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
Test-build pull requests with TestFlight. Usage: Add repository variables: Mandatory: - PR_NUMBER (Pull-request number in the nightscout/Trio repository) Optional: - ALTERNATIVE_BUNDLE_ID (the bundle ID which is associated with the TestFlight app you wish to build to)
bjornoleh
requested review from
dnzxy,
MikePlante1,
aug0211,
AndreasStokholm,
Sjoerd-Bo3 and
t1dude
as code owners
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.
The new
.github/workflows/PR_test_build.ymlworkflow checks out the pull request number that is entered as a repository variable.It is possible to optionally set an alternative bundle ID to not overwrite the TestFlight “production app” that one might be using live.
The checkout action starts with nightscout/Trio dev when setting up the git repository, so that the workflow is independent of any changes in the private fork.
Setup:
Add repository variables:
Mandatory:
Optional:
Usage:
Resolves #315