You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I tried to use vulture as part of our .pre-commmit-config.yaml file. I added the following snippet directly as documented in README:
repos:
- repo: https://github.com/jendrikseipp/vulturerev: 'v2.3'# or any later Vulture versionhooks:
- id: vulture
It failed with the following error:
Please pass at least one file or directory
While I fixed it by passing . as an argument in args section or by using pass_filenames: true, I feel this is a general enough to be included as part of the hook definition. Can you please change this?
Or, if there are any issues with that, is it possible to at least update the documentation with a working snippet? I think that will be very helpful for other users.
The text was updated successfully, but these errors were encountered:
I read up on this issue again and found the reason why things are configured the way they are: with pass_filenames: true pre-commit will only check modified files and therefore produce many false positives (see #244). While researching this, I found pre-commit run --all-files but I think the current solution of requiring the user to specify the files leads to better results.
I don't see a better solution than the status quo, so I'm closing this PR. But we can definitely reopen it when we find a better solution.
I tried to use
vulture
as part of our.pre-commmit-config.yaml
file. I added the following snippet directly as documented in README:It failed with the following error:
While I fixed it by passing
.
as an argument inargs
section or by usingpass_filenames: true
, I feel this is a general enough to be included as part of the hook definition. Can you please change this?https://github.com/jendrikseipp/vulture/blob/master/.pre-commit-hooks.yaml#L7
Or, if there are any issues with that, is it possible to at least update the documentation with a working snippet? I think that will be very helpful for other users.
The text was updated successfully, but these errors were encountered: