xcode-cloud-single-track-cilisted

# Xcode Cloud Single-Track CI ## When to invoke - Starting a new Apple-platform project and setting up CI. - Deciding between GitHub Actions and Xcode Cloud. - Writing `ci_scripts/ci_post_clone.sh` / `ci_pre_xcodebuild.sh` / `ci_post_xcodebuild.sh`. - Bumping the Xcode version and handling snapshot baselines. - User asks "how to split PR / Main / Release workflow", "auto-upload to TestFlight or not". ## Default decisions ### Single-track on Xcode Cloud - **GitHub Actions is not enabled yet** — wait for real pain (PR metadata rules, external lint jobs, Selective Testing, etc.) to appear. - The repo is hosted on GitHub, but CI runs on Xcode Cloud. ### 4 workflows | Workflow | Trigger | Action | |---|---|---| | **PR CI** | PR open / push — Pull Request Changes start condition (Xcode Cloud merges the PR with the target branch before building) | Build + Test (unit / integration with fakes / snapshot) | | **Main CI** | Merge to `main` | Build + Archive + upload to internal TestFlight; **do not re-run tests** (already verified by PR CI in pre-merged state) | | **Release** | git tag `v*` | Build + upload to App Store Connect (manual submission for review) | | **Periodic / Manual** | Scheduled + manual trigger | Project-specific batch jobs (nightly export, metadata updates, etc.) | > **Scheduling granularity caveat**: Xcode Cloud's "On a Schedule" start condition lets you specify the frequency, time, and branch (Apple's own example: "every business day at 10:00 p.m."); it does