build_loop workflow: add template for build on push and on schedule #38
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
…schedule
Includes comments with instructions for un-commenting to enable builds on push and automated builds every two months
on:
#push:
#schedule:
#- cron: '0 17 1 */2 *' # Runs at 17:00 UTC on the 1st in Jan, Mar, May, Jul, Sep and Nov.
|
As I see, provisioning profiles will not be renewed. Is that a problem? |
Contributor
Author
|
I still don't know how renewal of provisioning profiles works for TestFlight distribution. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
Includes comments with instructions for un-commenting to enable builds on push and automated builds every two months:
on:
workflow_dispatch:
#push:
#schedule:
#- cron: '0 17 1 */2 *' # Runs at 17:00 UTC on the 1st in Jan, Mar, May, Jul, Sep and Nov.
TestFlight builds must be renewed every 90 days, this is a way to automate repeated builds every two months. Building on push will also make updating a one-click task (sync fork in GitHub triggers build).
LoopDocs can hold the instructions for how to activate this feature (un-commenting the relevant lines).