7686989fc8
See https://pre-commit.com/#confining-hooks-to-run-at-certain-stages > If you are authoring a tool, it is usually a good idea to provide an appropriate `stages` property. For example a reasonable setting for a linter or code formatter would be `stages: [pre-commit, pre-merge-commit, pre-push, manual]`. Co-authored-by: Jelle Zijlstra <jelle.zijlstra@gmail.com>
23 lines
799 B
YAML
23 lines
799 B
YAML
# Note that we recommend using https://github.com/psf/black-pre-commit-mirror instead
|
|
# This will work about 2x as fast as using the hooks in this repository
|
|
- id: black
|
|
name: black
|
|
description: "Black: The uncompromising Python code formatter"
|
|
entry: black
|
|
stages: [pre-commit, pre-merge-commit, pre-push, manual]
|
|
language: python
|
|
minimum_pre_commit_version: 2.9.2
|
|
require_serial: true
|
|
types_or: [python, pyi]
|
|
- id: black-jupyter
|
|
name: black-jupyter
|
|
description:
|
|
"Black: The uncompromising Python code formatter (with Jupyter Notebook support)"
|
|
entry: black
|
|
stages: [pre-commit, pre-merge-commit, pre-push, manual]
|
|
language: python
|
|
minimum_pre_commit_version: 2.9.2
|
|
require_serial: true
|
|
types_or: [python, pyi, jupyter]
|
|
additional_dependencies: [".[jupyter]"]
|