CI: run the tests, the Swift build and the smoke check on every pull request - #1
Merged
Conversation
Until now the only workflow ran on a tag push, so a pull request carried no checks at all. This runs what a release would run, minus the DMG: cargo test, the bindings regenerated by build-core.sh, the SwiftPM build, and StudioSmoke against a real Stockfish — on the same macos-15 runner, so a green check here means the release build gets through too. The structural work that follows (per-window databases, native tabs) touches the write-back path, and it is going in as pull requests precisely so it can be reviewed and reverted as a unit. A check that means something is the first half of that. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01F9o9DSzZas4GsekCpG5M8T
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.
Until now the only workflow ran on a tag push, so a pull request carried no checks at all.
This runs what a release would run, minus the DMG —
cargo test, bindings regenerated bybuild-core.sh, the SwiftPM build, andStudioSmokeagainst a real Stockfish — on the same macos-15 runner, so a green check here means the release build gets through too.The structural work that follows (per-window databases, native tabs) touches the write-back path and is going in as pull requests precisely so it can be reviewed and reverted as a unit. A check that means something is the first half of that.
🤖 Generated with Claude Code
https://claude.ai/code/session_01F9o9DSzZas4GsekCpG5M8T