Skip to content

Run macOS CI on Minerva for verified commits - #5

Open
RISCfuture wants to merge 1 commit into
mainfrom
ci/minerva
Open

RISCfuture wants to merge 1 commit into
mainfrom
ci/minerva

Conversation

@RISCfuture

Copy link
Copy Markdown
Contributor

Each workflow gains a route job from RISCfuture/ci-workflows 1.1.0
(minerva-route.yml). It sends macOS jobs to the self-hosted Minerva
runner only for verified commits from RISCfuture, and keeps the hosted
labels for forks, other actors and unverified commits.

The Build, documentation and Periphery jobs use the macOS 26 pool
output, since they only build, generate DocC or index and never execute
a macOS 27 product. The SwiftLint job uses the macOS 26 pool through the
macos-latest output, so brew install swiftlint works. Swift 6.4 is the
only Swift version requested, which setup-swift supports on that pool.
The swift-format job runs in a Linux container and is unchanged.

No job runs macOS 27 tests, so none stays hosted for lack of Homebrew
and none uses the macOS 27 pool. The route jobs only grant contents:
read; the workflows have no workflow-level Pages permissions to scope.
There are no XCUITestKit callers.

🤖 Generated with Claude Code

Each workflow gains a route job from RISCfuture/ci-workflows 1.1.0
(minerva-route.yml). It sends macOS jobs to the self-hosted Minerva
runner only for verified commits from RISCfuture, and keeps the hosted
labels for forks, other actors and unverified commits.

The Build, documentation and Periphery jobs use the macOS 26 pool
output, since they only build, generate DocC or index and never execute
a macOS 27 product. The SwiftLint job uses the macOS 26 pool through the
macos-latest output, so brew install swiftlint works. Swift 6.4 is the
only Swift version requested, which setup-swift supports on that pool.
The swift-format job runs in a Linux container and is unchanged.

No job runs macOS 27 tests, so none stays hosted for lack of Homebrew
and none uses the macOS 27 pool. The route jobs only grant contents:
read; the workflows have no workflow-level Pages permissions to scope.
There are no XCUITestKit callers.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant