pre-commit-hooks | Standardizing our code quality tooling hammer_and_wrench | Code Analyzer library

The pre-commit hook will use a way of iterating over the files in the changeset. There's probably something like git ls-files in there. If you use git ls-files -c then it will just show you the cached changes (the default) -- if you use git ls-files -o then it will show uncommitted (other) files as well.

If you're re-using someone else's hooks, then you'll need to investigate those hooks to determine if there's a way they can selectively disable the changes.

yes, they overwrite receiving their defaults from .pre-commit-hooks.yaml

from the docs

All optional keys will receive their default from the repository's configuration.

if you want to specify arguments that are ~always honored, specify them in entry such as entry: autopep8 -i (this can still be overridden by the consuming repository, though it is less likely)

I dug a bit deeper in dnephin's hooks and this change to run-go-vet.sh solved my problem

Usually you rely on the remote repository to provide the configuration (such that you don't need all of the args / entry / etc. setup

for example if you want to use style-files from the repository you've listed you'd set this in your .pre-commit-config.yaml:

It appears you're using black and double-quote-strings-fixer together

• the former likes double quoted strings in python (you can disable this by configuring black to skip-string-normalization in pyproject.toml)
• the latter likes single quoted strings in python (you can remove it if you'd like double quoted strings)

If two formatters fight, the end result will be a failure as pre-commit checks to make sure everything resolves

disclaimer: I'm the author of pre-commit and pre-commit-hooks

If you fat-finger a dash after the -n number like -n -32, pytest will complain about a missing --tx option. In other words the number after -n cannot be negative and what you want to use instead is -n 32.

--tx is normally used like so to invoke a Python2.7 subprocess:

disclaimer: I'm the author of two of the tools in question (pre-commit, flake8-typing-imports) and the maintainer of the other (flake8)

the TYP005 code comes from flake8-typing-imports

there are two options for indicating your minimum supported version to flake8-typing-imports, the first is a command line argument / flake8 setting:

You shouldn't need to clone each repository manually and use local hooks in the way you're doing -- if you have clone access during build time you should be able to do the normal installation approach

To ensure all of the hooks are pre-installed, you'll want to run pre-commit install-hooks as one of the commands in your dockerfile

This will ensure that all of the hook executables are properly cached in your image and then will be available later when you run pre-commit run ...

disclaimer: I'm the author of pre-commit

because you're using language: python pre-commit will create an isolated environment to run that hook

you can add things to the environment by using additional_dependencies for example: