Some out-of-the-box hooks for pre-commit.
See also: https://github.com/pre-commit/pre-commit
Using pre-commit-hooks with pre-commit
Add this to your
- repo: https://github.com/pre-commit/pre-commit-hooks rev: v4.0.1 # Use the ref you want to point at hooks: - id: trailing-whitespace # - id: ...
Prevent giant files from being committed.
- Specify what is "too large" with
- Limits checked files to those indicated as staged for addition by git.
git-lfsis installed, lfs files will be skipped (requires
--enforce-all- Check all listed files not just those staged for addition.
Simply check whether files parse as valid python.
Require literal syntax when initializing empty or zero Python builtin types.
- Allows calling constructors with positional arguments (e.g.,
- Allows calling constructors from the
__builtin__) namespace (
- Ignore this requirement for specific builtin types with
dictkeyword syntax with
Check for files with names that would conflict on a case-insensitive filesystem like MacOS HFS+ or Windows FAT.
Checks for a common error of placing code before the docstring.
Checks that non-binary executables have a proper shebang.
Attempts to load all json files to verify syntax.
Check for files that contain merge conflict strings.
Checks that scripts with shebangs are executable.
Checks for symlinks which do not point to anything.
Attempts to load all TOML files to verify syntax.
Ensures that links to vcs websites are permalinks.
--additional-github-domain DOMAIN- Add check for specified domain. Can be repeated multiple times. for example, if your company uses GitHub Enterprise you may use something like
Attempts to load all xml files to verify syntax.
Attempts to load all yaml files to verify syntax.
--allow-multiple-documents- allow yaml files which use the multi-document syntax
--unsafe- Instead of loading the files, simply parse them for syntax. A syntax-only check enables extensions and unsafe constructs which would otherwise be forbidden. Using this option removes all guarantees of portability to other yaml implementations. Implies
Check for debugger imports and py37+
breakpoint() calls in python source.
Detects symlinks which are changed to regular files with a content of a path which that symlink was pointing to. This usually happens on Windows when a user clones a repository that has symlinks but they do not have the permission to create symlinks.
Checks for the existence of AWS secrets that you have set up with the AWS CLI. The following arguments are available:
--credentials-file CREDENTIALS_FILE- additional AWS CLI style configuration file in a non-standard location to fetch configured credentials from. Can be repeated multiple times.
--allow-missing-credentials- Allow hook to pass when no credentials are detected.
Checks for the existence of private keys.
This hook replaces double quoted strings with single quoted strings.
Makes sure files end in a newline and only a newline.
removes UTF-8 byte order marker
# -*- coding: utf-8 -*- to the top of python files.
- To remove the coding pragma pass
--remove(useful in a python3-only codebase)
Sort the lines in specified files (defaults to alphabetical). You must provide list of target files as input to it. Note that this hook WILL remove blank lines and does NOT respect any comments.
Prevent addition of new git submodules.
Replaces or checks mixed line ending.
auto- Replaces automatically the most frequent line ending. This is the default argument.
lf- Forces to replace line ending by respectively CRLF and LF.
- This option isn't compatible with git setup check-in LF check-out CRLF as git smudge this later than the hook is invoked.
no- Checks if there is any mixed line ending without modifying any file.
Assert that files in tests/ end in
args: ['--django']to match
Protect specific branches from direct checkins.
args: [--branch, staging, --branch, master]to set the branch. Both
mainare protected by default if no branch argument is set.
--branchmay be specified multiple times to protect multiple branches.
--patterncan be used to protect branches that match a supplied regex (e.g.
--pattern, release/.*). May be specified multiple times.
no-commit-to-branch is configured by default to
always_run. As a result, it will ignore any setting of
always_run: false to allow this hook to be skipped according to these file filters. Caveat: In this configuration, empty commits (
git commit --allow-empty) would always be allowed by this hook.
Checks that all your JSON files are pretty. "Pretty" here means that keys are sorted and indented. You can configure this with the following commandline options:
--autofix- automatically format json files
--indent ...- Control the indentation (either a number for a number of spaces or a string of whitespace). Defaults to 2 spaces.
--no-ensure-asciipreserve unicode characters instead of converting to escape sequences
--no-sort-keys- when autofixing, retain the original key ordering (instead of sorting the keys)
--top-keys comma,separated,keys- Keys to keep at the top of mappings.
Sorts entries in requirements.txt and removes incorrect entry for
Sorts simple YAML files which consist only of top-level keys, preserving comments and blocks.
sort-simple-yaml by default matches no
files as it enforces a very specific format. You must opt in to this by setting
files, for example:
- id: sort-simple-yaml files: ^config/simple/
Trims trailing whitespace.
- To preserve Markdown hard linebreaks use
args: [--markdown-linebreak-ext=md](or other extensions used by your markdownfiles). If for some reason you want to treat all files as markdown, use
- By default, this hook trims all whitespace from the ends of lines. To specify a custom set of characters to trim instead, use
args: [--chars,"<chars to trim>"].
Deprecated / replaced hooks
check-byte-order-marker: instead use fix-byte-order-marker
As a standalone package
If you'd like to use these hooks, they're also available as a standalone package.
pip install pre-commit-hooks