Add per-commit build check#3
Merged
Merged
Conversation
Co-authored-by: Codex <noreply@openai.com> Ai-assisted: true
Collaborator
Author
|
@codex review |
Collaborator
Author
|
@builderbot review |
|
To use Codex here, create a Codex account and connect to github. |
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.
What changed?
Adds a
BuildGitHub Actions workflow for Catch. The workflow runs on pushes tomainand pull requests targetingmain, selects an installed Xcode 26 toolchain for Swift tools 6.2, then runs the SwiftPM build and test suite.Adds a short README note explaining the CI workflow, keeping release packaging separate, and calling out the GitHub branch-protection setting needed if the check should block merges.
Why?
The repository only had release packaging automation, so ordinary commits and pull requests did not get a build/test check. This adds a minimal per-commit validation path without mixing release artifact creation into CI.
How is it tested?
Workflow syntax validation. SwiftPM build and test.
Focused existing validation:
main.🤖 This PR was authored with an agent.