From ae75603c8484f72ee283432bceb61773b6578eba Mon Sep 17 00:00:00 2001 From: mikael Date: Mon, 6 Jul 2026 13:45:49 +0200 Subject: [PATCH] Clarify scheduled build documentation --- CONTRIBUTING.md | 2 +- fastlane/testflight.md | 12 ++++++------ 2 files changed, 7 insertions(+), 7 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index b708ff16d8..ed1796ba7f 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -63,7 +63,7 @@ Loop is a collaborative project, and contributions of all kinds are welcome. Whe - Update docstrings when your change affects setup, configuration, behavior, workflows, or troubleshooting. - Keep documentation changes clear and practical. -- ocumentation contributions are just as valuable as code contributions. +- Documentation contributions are just as valuable as code contributions. ## Branches, commits, and pull requests diff --git a/fastlane/testflight.md b/fastlane/testflight.md index b44f07df07..5f30b5445d 100644 --- a/fastlane/testflight.md +++ b/fastlane/testflight.md @@ -236,9 +236,9 @@ If you choose not to have automatic building enabled, be sure the `GH_PAT` has ` ### Modify scheduled building and synchronization -You can modify the automation by creating and using some variables. +You can modify the automation by creating and using repository variables. -To configure the automated build more granularly involves creating up to two environment variables: `SCHEDULED_BUILD` and/or `SCHEDULED_SYNC`. See [How to configure a variable](#how-to-configure-a-variable). +To configure the automated build more granularly, create up to two repository variables: `SCHEDULED_BUILD` and/or `SCHEDULED_SYNC`. See [How to configure a variable](#how-to-configure-a-variable). Note that the weekly build actions will continue, but the actions are modified if one or more of these variables is set to false. **A successful Action Log will still appear, even if no automatic activity happens**. @@ -264,9 +264,9 @@ Note that the weekly build actions will continue, but the actions are modified i - Type `SCHEDULED_BUILD` in the "Name" field - Type `false` in the "Value" field - Click the green `Add variable` button to save. -7. To disable scheduled syncing, add a variable: +6. To disable scheduled syncing, add a variable: - Click on the green `New repository variable` button (upper right) - - - Type `SCHEDULED_SYNC` in the "Name" field + - Type `SCHEDULED_SYNC` in the "Name" field - Type `false` in the "Value" field - Click the green `Add variable` button to save @@ -276,8 +276,8 @@ Your build will run on the following conditions: - If updates are detected, it will update your repository and build - If it is the second Sunday of the month, it will build even when no changes are detected - If you disable any automation (both variables set to `false`), no updates or building happens when the build action runs -- If you disabled just scheduled synchronization (`SCHEDULED_SYNC` set to`false`), it will still build once a month, but no update will happen -- If you disabled just scheduled build (`SCHEDULED_BUILD` set to`false`), it will run once weekly, to check for changes; if there are changes, it will update and build +- If you disabled just scheduled synchronization (`SCHEDULED_SYNC` set to `false`), it will still build once a month, but no update will happen +- If you disabled just scheduled build (`SCHEDULED_BUILD` set to `false`), it will run once weekly, to check for changes; if there are changes, it will update and build ## What if I build using more than one GitHub username