[CI] Add xcodebuild gate for PRs (#33)#37
Merged
Conversation
Adds .github/workflows/build.yml — runs xcodebuild against the tabby scheme on every PR into main and every push to main. Fails the check on compile errors so they're caught before review. - Pinned to `latest-stable` Xcode via setup-xcode; intentional bump point when the project moves versions. - Debug config for speed; same compile surface as Release. - CODE_SIGNING_ALLOWED=NO because runners lack the dev cert. - Concurrency guard cancels stale runs on rapid pushes. Refs #33
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
1 participant
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.
Summary
First CI check:
xcodebuild buildon every PR intomainand on pushes tomain. Compile errors now fail the PR gate before a reviewer has to look at it.What's in the workflow
macos-latestsetup-xcode@v1tolatest-stable. Explicit bump point — GitHub-hosted images swap their default Xcode without notice and that surfaces as mystery-red or mystery-green builds.tabby, Debug config.CODE_SIGNING_ALLOWED=NO. Runners don't have the dev cert; Automatic signing would otherwise fail the step. Check stays focused on compile correctness.What you'll see after merge
xcodebuildoutput in the run log.mainafter merge — so a future README badge can reflect current main health.Follow-ups (separate PRs)
Refs
Refs #33