[WIP] Don't run hooks on submodule roots #254
Closed
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.
git tracks submodules like files. In particular, the roots of submodules appear in the output of
git ls-files
. This means we get weird errors like:The only way to avoid this right now is to explicitly exclude submodule paths in you
.pre-commit-config.yaml
(or to modify every hook to check if an input file is actually a file, which seems bad).We can exclude these with a slightly more complicated
ls-files
command.I didn't test this extensively or even check if the tests still pass, mostly just looking to see if this looks like a reasonable solution. If it does I'll go ahead and write real tests (and test it on some older git versions to make sure it still works).