Update ios-dev-builds.md to clarify xcodebuild vs Fastlane #252
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix/ios-dev-builds-docs"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Clarifies that the production iOS build pipeline uses raw
xcodebuild, not Fastlane. Adds cross-references toios-pipeline.mdand reframes the Fastlane section as a local dev convenience rather than the canonical build path.Changes
docs/ios-dev-builds.md-- Added callout at top cross-referencing ios-pipeline.md for production builds; annotated Fastlane prerequisite to note it is for local dev only; renamed Fastlane section to "Fastlane Setup (Local Dev Only)" with a note explaining why production uses xcodebuild and linking to the "Why Not Fastlane?" rationaleREADME.md-- Updated ios-dev-builds table description from "TestFlight, wireless install, Fastlane setup" to "Local dev builds, wireless install, Fastlane reference"Test Plan
Review Checklist
Related Notes
None.
Related
Closes #251
Review
Docs-only change, 2 files, +7 / -3. Reviewed the diff against
ios-pipeline.mdfor consistency.Checked
ios-dev-builds.mdcorrectly points toios-pipeline.mdfor production builds.ios-pipeline.md#why-not-fastlaneresolves correctly -- the heading in ios-pipeline.md is## Why Not Fastlane?.Findings
No issues found.
VERDICT: APPROVE
PR #252 Review
DOMAIN REVIEW
Tech stack: Markdown documentation (no code changes).
This is a docs-only PR that touches two files:
docs/ios-dev-builds.mdandREADME.md. The changes reframe Fastlane as a local dev convenience rather than the production build tool, and add cross-references todocs/ios-pipeline.md(introduced in merged PR #250).Link verification:
ios-pipeline.md-- exists on main (introduced by PR #250, merged). Valid.ios-pipeline.md#why-not-fastlane-- the## Why Not Fastlane?section exists in that file. Anchor is valid.pipeline.mdin the opening paragraph is preserved and valid.Content accuracy:
xcodebuild, not Fastlane. This is consistent withdocs/ios-pipeline.mdand the updateddocs/pipeline.md(both from PR #250).xcodebuild") is accurate and does not remove the prerequisite -- it contextualizes it.produceaction limitation documented inios-pipeline.md.No content was removed. All existing Fastlane documentation (Appfile, Fastfile, Matchfile table; first-time setup instructions; lane definitions; troubleshooting) is preserved. Only framing was changed.
BLOCKERS
None.
NITS
The
README.mdchange updates the Development section's iOS Dev Builds description, but the same file also has a line in the "Infrastructure & Deploy" section (added by PR #250) that references[iOS Pipeline](docs/ios-pipeline.md) | Turbo Native build, signing, App Store Connect, TestFlight. This is fine and consistent -- just noting that the two docs are now properly differentiated in the table of contents.Minor: the blockquote note in the Fastlane section is quite long (3 sentences). Consider breaking it into a callout with a short summary line and a details/rationale sentence. Non-blocking -- the current version is clear enough.
SOP COMPLIANCE
Closes #251is present in the Related sectionPROCESS OBSERVATIONS
Clean documentation maintenance PR. The change correctly follows up on PR #250 (which introduced
ios-pipeline.mdand updatedpipeline.md) by reconciling the remaining stale Fastlane references inios-dev-builds.md. This prevents documentation drift where one doc says "use Fastlane" and two others say "use xcodebuild." Low change failure risk -- no code, no infrastructure.VERDICT: APPROVED