Skip to content

Commit

Permalink
Add more pre-commit checks
Browse files Browse the repository at this point in the history
  • Loading branch information
hugovk committed Oct 11, 2023
1 parent 704cb67 commit da786e7
Show file tree
Hide file tree
Showing 2 changed files with 18 additions and 1 deletion.
17 changes: 17 additions & 0 deletions .pre-commit-config.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -29,5 +29,22 @@ repos:
flake8-logging,
]

- repo: https://github.com/pre-commit/pygrep-hooks
rev: v1.10.0
hooks:
- id: python-check-blanket-noqa

- repo: https://github.com/pre-commit/pre-commit-hooks
rev: v4.5.0
hooks:
- id: check-case-conflict
- id: check-executables-have-shebangs
- id: check-merge-conflict
- id: check-json
- id: check-toml
- id: check-yaml
- id: debug-statements
- id: end-of-file-fixer
- id: trailing-whitespace
ci:
autoupdate_schedule: quarterly
2 changes: 1 addition & 1 deletion readme.rst
Original file line number Diff line number Diff line change
Expand Up @@ -18,7 +18,7 @@ of the maintenance branches (``3.6``, ``3.5``, ``2.7``).
workflow as CPython. See the configuration file options below for more details.

The maintenance branch names should contain some sort of version number (X.Y).
For example: ``3.6``, ``3.5``, ``2.7``, ``stable-2.6``, ``2.5-lts``, are all
For example: ``3.6``, ``3.5``, ``2.7``, ``stable-2.6``, ``2.5-lts``, are all
supported branch names.

It will prefix the commit message with the branch, e.g. ``[3.6]``, and then
Expand Down

0 comments on commit da786e7

Please sign in to comment.