You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/browser/automatic.md
+10-5Lines changed: 10 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -56,17 +56,21 @@ The modified design for the build action found in `Loop v3.8.2` and newer is doc
56
56
57
57
#### Updated Build Features
58
58
59
-
The code that controls the build process was streamlined and enhanced to have these features:
59
+
The code that controls the build process was streamlined and enhanced. It runs every Sunday at a time when *GitHub* is not impacted. The portion of the action that decides whether to build or not completes in a few seconds.
60
+
61
+
**Build when**
62
+
63
+
* updates are detected
64
+
* it is the second Sunday of the month
65
+
66
+
**Other features**
60
67
61
-
* build when updates are found on any Sunday
62
-
* build on the second Sunday of the month regardless of update status
63
-
* rearrange the order so the check whether to build takes a few seconds
64
-
* longer processes are skipped when build is skipped
65
68
* remove the concept of alive branches
66
69
* remove the requirement that your fork name match the upstream repository name
67
70
* enable any branch in your fork to be updated if the upstream repository has the same branch
68
71
* if you choose to have a special branch in your fork set to default, the automatic check for updates works for that special branch
69
72
73
+
70
74
??? question "Do you want to know more? (Click to open/close)"
71
75
**Build Action Redesign**
72
76
@@ -118,6 +122,7 @@ In April 2025, GitHub disallowed using the build action to automatically add com
118
122
Once you update to v3.8.2 or newer, references to `alive branches` are removed from the build action.
119
123
120
124
> * If you have alive branches (`alive`, `alive-dev` or `alive-main`) you may delete them if you choose
125
+
* Only delete alive branches after your default branch is updated to the new version
0 commit comments