Deploying to gh-pages from @ a059eee 🚀

gh-actions/automatic/index.html

@@ -3462,20 +3462,31 @@ <h2 id="overview">Overview<a class="headerlink" href="#overview" title="Anchor l
 <p><strong>After the next release of the <em><abbr title="With a capital L, Loop is one of several do-it-yourself artifical pancreas systems">Loop</abbr></em> app (version 3.4.0), this page will be required for all versions when building with a browser.</strong></p>
 <p><strong>Before that release, this page is only relevant when building the <code>dev</code> <abbr title="version of code within a single repository or workspace repository">branch</abbr> with a browser and only when the <code>dev</code> <abbr title="version of code within a single repository or workspace repository">branch</abbr> is the default <abbr title="version of code within a single repository or workspace repository">branch</abbr>.</strong></p>
 <h2 id="modify-automatic-building">Modify Automatic Building<a class="headerlink" href="#modify-automatic-building" title="Anchor link to this Header on this Page">&para;</a></h2>
-<p>For someone using <a href="../build-dev-browser/">development code</a> for their own use, they probably want to decide when to update their <code>fork</code> to the most recent <abbr title="a formal change to files in a repository; each commit has an alphanumeric identifier (SHA-1)">commit</abbr>. They can still have the advantage of automatic building without automatic updates. There may be other configurations someone would choose. These options are added to <abbr title="Latest release with major updates">Loop 3</abbr>.3.0 (<code>dev</code> <abbr title="version of code within a single repository or workspace repository">branch</abbr>) and later.</p>
+<p>For someone using <a href="../build-dev-browser/">development code</a> for their own use, they could decide to choose when to update their <code>fork</code> to the most recent <abbr title="a formal change to files in a repository; each commit has an alphanumeric identifier (SHA-1)">commit</abbr>. They can still have the advantage of automatic building without automatic updates; in other words, they want a new build added to <abbr title="a method to distribute apps without direct connection">TestFlight</abbr> every month. There may be other configurations someone would choose. These options are available starting with <abbr title="Latest release with major updates">Loop 3</abbr>.3.0 (<code>dev</code> <abbr title="version of code within a single repository or workspace repository">branch</abbr>) and later.</p>
 <p>You can affect the default behavior:</p>
 <ol>
 <li><a href="#modify-automatic-schedule">Modify Automatic Schedule</a></li>
 <li><a href="#disable-automatic-actions">Disable Automatic <abbr title="a custom application for the GitHub Actions platform that performs a complex but frequently repeated task; specifically used to build Loop from a browser">Actions</abbr></a></li>
 </ol>
 <h3 id="modify-automatic-schedule">Modify Automatic Schedule<a class="headerlink" href="#modify-automatic-schedule" title="Anchor link to this Header on this Page">&para;</a></h3>
+<p>This is an optional step. If you are happy with the automatic sync and update, you are done with this page.</p>
+<details class="tip">
+<summary>Instructions to Modify the Automatic <abbr title="a custom application for the GitHub Actions platform that performs a complex but frequently repeated task; specifically used to build Loop from a browser">Actions</abbr> (Click to Open/Close)</summary>
 <p>You can modify the automation by creating and using some variables.</p>
-<p>To configure the automated build more granularly involves creating up to two environment variables: <code>SCHEDULED_BUILD</code> and/or <code>SCHEDULED_SYNC</code>. See <a href="#how-to-configure-a-variable">How to configure a variable</a>. </p>
+<p>To configure the automated build more granularly involves creating up to two environment variables: <code>SCHEDULED_BUILD</code> and/or <code>SCHEDULED_SYNC</code>. See <a href="#how-to-configure-a-variable">How to configure a variable</a>.</p>
 <p>Note that the weekly and monthly <code>Build Loop</code> actions will continue, but the actions are modified if one or more of these variables is set to false. <strong>A successful Action Log will still appear, even if no automatic activity happens</strong>.</p>
 <ul>
-<li>If you want to manually decide when to update your <abbr title="contains project files and each file's revision history">repository</abbr> to the latest <abbr title="a formal change to files in a repository; each commit has an alphanumeric identifier (SHA-1)">commit</abbr>, but you want the monthly builds and keep-alive to continue: set <code>SCHEDULED_SYNC</code> to false and either do not create <code>SCHEDULED_BUILD</code> or set it to true</li>
-<li>If you want to only build when an update has been found: set <code>SCHEDULED_BUILD</code> to false and either do not create <code>SCHEDULED_SYNC</code> or set it to true<ul>
+<li>If you want to manually decide when to update your <abbr title="contains project files and each file's revision history">repository</abbr> to the latest <abbr title="a formal change to files in a repository; each commit has an alphanumeric identifier (SHA-1)">commit</abbr>, but you want the monthly builds and keep-alive to continue:<ul>
+<li>create the variable <code>SCHEDULED_SYNC</code> and set it to false</li>
+<li>either do not create the variable <code>SCHEDULED_BUILD</code> or set it to true</li>
+<li>If you are building the <code>dev branch</code> at a time when there is a lot of activity in that <abbr title="version of code within a single repository or workspace repository">branch</abbr>, you may want this configuration</li>
+</ul>
+</li>
+<li>If you want to only build when an update has been found:<ul>
+<li>either do not create the variable <code>SCHEDULED_SYNC</code> or set it to true</li>
+<li>create the variable <code>SCHEDULED_BUILD</code> and set it to false</li>
 <li><strong>Warning</strong>: if no updates to your default <abbr title="version of code within a single repository or workspace repository">branch</abbr> are detected within 90 days, your previous <abbr title="a method to distribute apps without direct connection">TestFlight</abbr> build may expire requiring a manual build</li>
+<li>During a time when updates are not happening frequently, this is not a good choice</li>
 </ul>
 </li>
 </ul>
@@ -3489,19 +3500,19 @@ <h3 id="modify-automatic-schedule">Modify Automatic Schedule<a class="headerlink
 </thead>
 <tbody>
 <tr>
-<td><code>true</code> (or NA)</td>
-<td><code>true</code> (or NA)</td>
-<td>keep-alive, weekly update check (auto update/build), monthly build with auto update</td>
+<td><code>true</code> (or N/A)</td>
+<td><code>true</code> (or N/A)</td>
+<td>This is the default:<br>keep-alive, weekly update check (auto update/build), monthly build with auto update</td>
 </tr>
 <tr>
-<td><code>true</code> (or NA)</td>
 <td><code>false</code></td>
-<td>keep-alive, weekly update check with auto update, only builds if update detected</td>
+<td><code>true</code> (or N/A)</td>
+<td>keep-alive, monthly build, no auto update</td>
 </tr>
 <tr>
+<td><code>true</code> (or N/A)</td>
 <td><code>false</code></td>
-<td><code>true</code> (or NA)</td>
-<td>keep-alive, monthly build, no auto update</td>
+<td>keep-alive, weekly update check with auto update, only builds if update detected</td>
 </tr>
 <tr>
 <td><code>false</code></td>
@@ -3510,6 +3521,7 @@ <h3 id="modify-automatic-schedule">Modify Automatic Schedule<a class="headerlink
 </tr>
 </tbody>
 </table>
+</details>
 <h3 id="how-to-configure-a-variable">How to configure a variable<a class="headerlink" href="#how-to-configure-a-variable" title="Anchor link to this Header on this Page">&para;</a></h3>
 <ol>
 <li>Go to the "Settings" tab of your LoopWorkspace <abbr title="contains project files and each file's revision history">repository</abbr>.</li>