add notes about Loop build action being disabled by GitHub

Author: marionbarker

docs/browser/automatic.md

@@ -15,9 +15,9 @@ The instructions provided for building with a browser include settings to automa
 !!! warning "Browser Build Disabled"
     We do not know why, but GitHub is disabling the Build Loop Action for LoopWorkspace even though the repository is not stale.
 
-    * We think it is associated with running too many builds at a busy time that requested too many runners (virtual computers)
-    * The redesigned build action for v3.8.2 should alleviate this
-    * We also plan to reach out to GitHub after people have transitioned to the v3.8.2 build schedule
+    * The automatic build actions should occur every Sunday
+        * The automatic build using the same code works for all OS-AID apps except for *Loop*
+        * See this [GitHub Discussion topic for details](https://github.com/orgs/community/discussions/181236)) 
 
 ### What Manual Action is Required?
 

docs/browser/bb-errors.md

@@ -156,9 +156,9 @@ Ignore the warnings - this does not affect the build.
 
 ### Manual Enable for Build Action May be Required
 
-The automatic build actions continue to happen on schedule, but starting May 2025, you may find your build action disabled by *GitHub*. (This might happen every 60 days, but it might happen sooner.) In that case, no build actually happens, no warning email is sent and a green checkmark (✅) appears beside a very short build action in which the actual build was skipped.
+The automatic build actions should occur every Sunday. They do for all OS-AID apps except for *Loop*.  ([We do not know why.](https://github.com/orgs/community/discussions/181236)) 
 
-If necessary, enable the build action at your repository as shown in the graphic below and then launch a manual build.
+For *Loop*, if your build action is being disabled, you need to manually enable the action at your repository as shown in the graphic below and then launch a manual build.
 
 ![fix a disabled build state](img/build-disabled-fix.png )
 

docs/browser/bb-overview.md

@@ -114,8 +114,8 @@ Once your build completes successfully:
 
 ### Automatic Updates
 
-!!! success "Set It and Forget It"
-    With Loop 3.4+, your app automatically rebuilds monthly (after initial setup). You just need to:
+!!! success "Check Status of Build Action Monthly"
+    The automatic build actions should occur every Sunday. They do for all OS-AID apps except for *Loop*, and even for *Loop*, some people are getting automatic builds.  ([We do not know why.](https://github.com/orgs/community/discussions/181236)) 
 
     * Keep your Apple Developer account active
     * Install updates from TestFlight when ready

docs/browser/bb-update.md

@@ -34,14 +34,14 @@
 
     Most users will start at [How to Update or Rebuild](#how-to-update-or-rebuild):
 
-    * If currently using verion 3.4.0 or newer, builds are automatic but you still need to do some actions:
+    * If currently using verion 3.4.0 or newer, builds are supposed to be automatic, but are being disabled by GitHub ([for Loop, not other OS-AID](https://github.com/orgs/community/discussions/181236)), so you should check the status monthly
+    * In addition to that monthly check, expect to do these actions:
         * Your *Apple Developer* account must be active
         * All agreements must be signed for your *Apple Developer* account
         * Once a year, you need to update renew certificates, but this is automatic with `Loop 3.6.0` and newer versions
 
     If you are running `Loop-dev`, be sure to review these instructions but modify for the branch you are using: refer to [Build Loop dev with Browser](build-dev-browser.md)
 
-
 ???+ question "FAQs (click to open/close)"
     - **"What is an update?"** Anytime you want to change versions or if your *TestFlight* build is about to expire, follow the instructions on this page.
     - **"Do I delete my old Loop app first?"** Definitely **not**! If you keep your Loop app on your phone, your Loop settings (and existing pod) will continue to work the same after the update. Seamless.

docs/browser/build-dev-browser.md

@@ -95,6 +95,10 @@ The [Automatic Update & Build](automatic.md){: target="_blank" } features are ap
 
 Most people should keep `main` as default and make a considered decision when to launch a manual build of the `dev` branch. At that time, it will automatically update to the latest `dev` commit unless you have modified your settings with special `Variables`: [Modify Automatic Building](automatic.md#modify-automatic-building){: target="_blank" }.
 
+> The automatic build actions should occur every Sunday. They do for all OS-AID apps except for *Loop*.  ([We do not know why.](https://github.com/orgs/community/discussions/181236)) 
+
+> See [Manual Enable for Build Action](bb-errors.md#manual-enable-for-build-action-may-be-required){: target="_blank" }
+
 ## Change Default `Branch`
 
 > **We recommend most users leave their default branch as `main`.**

docs/browser/intro-summary.md

@@ -54,7 +54,7 @@
 
 ???+ question "FAQs (click to open/close)"
     - **Do I need a Mac computer?** No. This can be done on any browser, although it will be easier using a computer or tablet than just using a phone.
-    - **Isn't it hard to build every 90 days?** The initial setup and installation take a lot of your focused time. But once you build, future updates and builds are automatic. You just need to keep your Apple Developer account up to date. Review any email that says a GitHub action failed - read the error and take action. For more information, see [Automatic Update & Build](automatic.md){: target="_blank" }.
+    - **Isn't it hard to build every 90 days?** The initial setup and installation take a lot of your focused time. But once you build, future updates and builds are really fast. You just need to keep your Apple Developer account up to date. Review any email that says a GitHub action failed - read the error and take action. For more information, see [Automatic Update & Build](automatic.md){: target="_blank" }.
     - **When do I have to kick off my automatic build?** Starting in May 2025, you may need to take an extra action after 60 days with no updates to the app: [Manual Action for Automatic Build](automatic.md#manual-action-for-automatic-build){: target="_blank" } 
     - **Can you explain the new automatic building?** There's a whole page on [Automatic Update & Build](automatic.md){: target="_blank" } for more explanations
     - **Can I use this for my child?** You, as the adult, can install using *TestFlight* on your child's phone. The explicit steps are provided at [Install on Phone: *TestFlight* for a Child](phone-install.md#testflight-for-a-child){: target="_blank" }.

docs/browser/phone-install.md

@@ -1,6 +1,12 @@
 ## General Installation Information
 
-**The *Loop* app must be built at least every 90 days when using a browser to build.** With version 3.4.0 and newer, the build is automatic (once a month or with a new release). It is recommended you manually install the new build using *TestFlight* at your convenience.
+**The *Loop* app must be built at least every 90 days when using a browser to build.** 
+
+> The automatic build actions should occur every Sunday. They do for all OS-AID apps except for *Loop*.  ([We do not know why.](https://github.com/orgs/community/discussions/181236)) 
+
+> See [Manual Enable for Build Action](bb-errors.md#manual-enable-for-build-action-may-be-required){: target="_blank" }
+
+It is recommended you manually install the new build using *TestFlight* at your convenience.
 
 After you [Build the *Loop* App](build-yml.md#build-the-loop-app){: target="_blank" } with a browser and you get the email that it is availble in *TestFlight*, you are ready to install on as many phones as you and your family members need.
 

docs/troubleshooting/dana-faq.md

@@ -110,7 +110,7 @@ But when you use a CGM like [NightScout remote CGM](../loop-3/add-cgm.md#nightsc
 
     * To save your changes to the "build_loop.yml", go to the Source Control tab on the left (should show up with a blue 1, see image below).
     Enter a message and press the green "Commit & Push"-button.
-    By pressing this button, GitHub will automatically make a new browser build for you and push it to TestFlight
+    By pressing this button, GitHub will automatically make a new browser build for you and push it to TestFlight (with the caveat that you might need to manually start the build)
     ![Github web ide example](./img/background-sound-web-ide.png)
 
 > If you have older code, before main v3.8.1 or dev v3.9.1, open the box above for instructions on a required modification.

docs/troubleshooting/loop-crashing.md

@@ -19,9 +19,7 @@ Your Loop app has an expiration date. The expiration date will depend on the bui
 
 ### Browser Build
 
-> Update to version 3.4 as soon as possible. The builds will then be automatic. So all you will need to do in install the latest build from *TestFlight* on your phone.
-
-If you are running an older version, you do not get prior warning that the app is about to expire, although you can look in the *TestFlight* app and it will tell you. An in-app warning is supplied with version 3.4.
+> With *Loop* 3.4 and newer, you will get an in-app notification when your build is about to expire. For many people, GitHub is disabling the automatic build once a month feature for Loop. Be sure to check once a month and kick off the build action if needed to make sure you always have a valid build in TestFlight.
 
 Please follow these steps to ensure you can build the app again: [How to Update or Rebuild](../browser/bb-update.md#how-to-update-or-rebuild){: target="_blank" }.