Repository navigation
Add a pre-push check suite - #23
Merged
Merged
Conversation
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.
Ported from the setup in enterprise-data-services. On push, one headless
claude -psession (read-only tools) runs three repo-local skills onorigin/main...<pushed sha>:A⚠️ finding blocks the push. The suite skips itself when
claudeis missing, the diff is empty, the push only deletes, or there's no verdict.SKIP=check-suite git pushbypasses it on purpose.The hook is now tracked in
.githooks/pre-push(ruff check, ruff format, pytest, then the suite). Enable it once per clone withgit config core.hooksPath .githooks. There's no new dependency.The last two commits are the linked-worktree test fixes also on #22.