Add multitool schema validation - #712
Open
be-student wants to merge 1 commit into
Open
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
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.
Closes #663.
This vendors the lockfile schema from
bazel-contrib/rules_multitooland adds a generatedcheck-multitoolpre-commit hook. The hook recognizesmultitool.lock.jsonat the repository root or in nested directories, and positive/negative fixtures cover schema validation and filename selection.The vendored schema includes its SHA-256 digest, upstream Apache-2.0 license, generated usage documentation, and changelog entry.
Validation:
env -u NO_COLOR .tox/py311/bin/coverage run -m pytest(615 passed, 17 skipped)uvx pre-commit run --all-files.tox/mypy/bin/mypy src/(with Click 8.2.1)uvx tox run -e docs