feat: Adds autobuild trigger workflow to avoid the auto-disabling on build loop job#461
Open
daghaian wants to merge 1 commit into
Open
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What changed
The Build Loop workflow was being automatically disabled by GitHub after each run (manual or scheduled), preventing subsequent scheduled builds from firing. The root cause is a known GitHub Actions behavior where workflows with a
scheduletrigger can be auto-disabled under certain conditions.Why
Scheduled builds were silently failing to run, which breaks the expected automated build cadence.
Solution
scheduletrigger from the Build Loop workflowtrigger_buildworkflow that owns the schedule, re-enables the Build Loop workflow before each run, and then dispatches it viaworkflow_dispatchThis sidesteps GitHub's auto-disable behavior by keeping the scheduled entry point in a separate, lightweight workflow that re-activates the primary one before triggering it.
Testing
trigger_buildand confirmed it re-enabled and dispatched Build Loop successfullyReview notes
The logic change is isolated to workflow files only — no app code is affected. The main thing worth validating is that the
workflow_dispatch+ re-enable sequence intrigger_buildis robust across the expected trigger scenarios (scheduled, manual).