@@ -322,7 +322,7 @@ you are aware of the existing issues beforehand.
322322
323323Install pre-commit hooks
324324========================
325- `pre-commit <https://pre-commit.com / >`_ hooks save time in the review process by
325+ `prek <https://prek.j178.dev / >`_ hooks save time in the review process by
326326identifying issues with the code before a pull request is formally opened. Most
327327hooks can also aide in fixing the errors, and the checks should have
328328corresponding :ref: `development workflow <development-workflow >` and
@@ -333,8 +333,8 @@ committed files, import order, and incorrect branching.
333333
334334Install pre-commit hooks ::
335335
336- python -m pip install pre-commit
337- pre-commit install
336+ python -m pip install prek
337+ prek install
338338
339339Hooks are run automatically after the ``git commit `` stage of the
340340:ref: `editing workflow<edit-flow> `. When a hook has found and fixed an error in a
@@ -343,11 +343,11 @@ file, that file must be *staged and committed* again.
343343Hooks can also be run manually. All the hooks can be run, in order as
344344listed in ``.pre-commit-config.yaml ``, against the full codebase with ::
345345
346- pre-commit run --all-files
346+ prek run --all-files
347347
348- To run a particular hook manually, run ``pre-commit run `` with the hook id ::
348+ To run a particular hook manually, run ``prek run `` with the hook id ::
349349
350- pre-commit run <hook id> --all-files
350+ prek run <hook id> --all-files
351351
352352
353353Please note that the ``mypy `` pre-commit hook cannot check the :ref: `type-hints `
0 commit comments