From da786e7595cccec3690127a60420b94e2418d1dd Mon Sep 17 00:00:00 2001 From: Hugo van Kemenade Date: Wed, 11 Oct 2023 15:00:39 +0200 Subject: [PATCH] Add more pre-commit checks --- .pre-commit-config.yaml | 17 +++++++++++++++++ readme.rst | 2 +- 2 files changed, 18 insertions(+), 1 deletion(-) diff --git a/.pre-commit-config.yaml b/.pre-commit-config.yaml index 340234a..a050535 100644 --- a/.pre-commit-config.yaml +++ b/.pre-commit-config.yaml @@ -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 diff --git a/readme.rst b/readme.rst index 7724ce5..612a226 100644 --- a/readme.rst +++ b/readme.rst @@ -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