Add CI: lint, format check, typecheck, and tests on PR - #15
Merged
Conversation
No GitHub Actions existed in this repo at all before this. Runs make check (ruff lint + format --check, ty typecheck) and make test (pytest) on every PR and on push to main/feature/batch-api/rc. Deliberately scoped to lint/checks/tests only - no publish automation. See the separate investigation into what a PyPI release workflow would need before that gets built. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DTXXBERPGEnYiYP4Mt3FjF
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.
Summary
No GitHub Actions existed in this repo at all before this. Adds a single workflow that runs on every PR and on push to
main/feature/batch-api/rc:make check— ruff lint + format check,tytypecheckmake test— pytestScoped deliberately to lint/checks/tests only, per request — no publish automation. Based off
feature/batch-api/rcsince that's wherepyproject.toml/uv(which this workflow needs) actually lives;mainstill has the oldsetup.py/requirements.txtstructure.Test plan
uv sync --all-extras,make check(clean),make test(123/123 pass)