Mark scheduled runs with nothing to build as cancelled instead of successful - #472
Merged
Merged
Conversation
Contributor
Author
Test✅ successful test ConfigurationUsed docs-test organization
|
Merged
marionbarker
added a commit
that referenced
this pull request
Jul 30, 2026
* Merge pull request #461 from daghaian-loop-org/add-build-autotrigger feat: create new build_loop_auto file to prevent disabling by GitHub * improve clarity: when build is skipped, run is canceled no green check mark is shown (#472) * update to fastlane 2.236.1 * update fastlane to 2.237.0 --------- Co-authored-by: David Aghaian <16483722+daghaian@users.noreply.github.com>
greyghost99
pushed a commit
to type1ghost/LoopWorkspace
that referenced
this pull request
Jul 30, 2026
yonatan-genai
added a commit
to yonatan-genai/LoopWorkspace
that referenced
this pull request
Sep 19, 2026
…auto.yml Upstream (LoopKit#461) split the workflow into a manual build_loop.yml and a scheduled build_loop_auto.yml, which conflicted with our scheduled-build customization and broke the weekly fork sync (merge conflict in build_loop.yml). Resolve by taking upstream's manual workflow as-is (plus the LAST_BUILD_DATE recording step so manual builds also reset the 30-day clock) and porting our Saturday 07:33 cron, the BUILD_DUE / LAST_BUILD_DATE 30-day rebuild check, and the record step onto the auto workflow, including its new cancel_when_no_build job (LoopKit#472). Claude-Session: https://claude.ai/code/session_01LRrpc74MEpTfZ48rnVFYJo
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
1 participant
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.
Problem
The scheduled weekly run checks for new commits and only builds when something changed (or when the monthly forced build is due). When there is nothing to build, the build jobs are skipped and the run still completes with a green check — indistinguishable at a glance from a successful build. Users who rely on the green status can believe they have a fresh build even when their last real build attempt failed.
Change
Copied the change from LoopFollow PR 705. See that PR for more information.
Status semantics after this change: