Repository navigation
ci: move trusted macOS builds to the M1 Max runner - #3
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.
Route Build & Test, SwiftLint and Format Check to the repository-scoped M1 Max runner, keeping all three required check names and every build/test/lint/format command. Use preprovisioned xcpretty, SwiftLint and SwiftFormat, explicit copied Xcode and job-local cached DerivedData instead of mutating shared Homebrew/gems or global xcode-select. Shell steps serialize through the shared helper.
This repository is public and the runner is a personal persistent machine. Job guards require the canonical repository, owner actor, owner-authored PR and same-repository head. Forks and other contributors cannot use this runner. Review/import trusted external changes into an owner-authored repository branch before requesting required CI; never dispatch an untrusted fork on this machine. Checkouts do not persist credentials and the workflow defaults to contents: read.
Validation: actionlint passes and job names/scope are preserved. Existing app code already fails current strict SwiftLint (51 violations) and SwiftFormat (24 files); those failures are preserved and no app formatting or lint rules were changed. Full Xcode checks remain required. The CI-only counterpart, including updater checks, was also applied to updater PR #2; signed release stays hosted behind the release environment.