Reuse local iOS builds and cancel superseded PR checks - #7
Merged
Merged
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.
Repeated development sessions can create separate iOS Derived Data trees for the same app, while repeated pushes to a pull request keep obsolete CI runs consuming runners.
The example now reuses its local build directory, and CI cancels checks for superseded PR commits.
ios/build/ddwithONLY_ACTIVE_ARCH=YESfor local builds, addios:build, and document Debug and isolated-directory overrides.AGENTS.md, imported byCLAUDE.md.Push runs use commit-specific groups so every main commit can satisfy the release and mirror gates.
Validation:
python3 -m unittest discover -s scripts/tests: 36 tests passed without native compilation.git diff --checkpassed.Native builds,
npm run check(TypeScript output and Codegen), and device QA were intentionally skipped at the user's request.No simulator, emulator, or physical device was used.
Configuration checks do not establish GitHub scheduling behavior or native runtime behavior; regular PR CI remains responsible for remote build verification.