Skip to content

PYTHON-6263 Remove the blacken-docs pre-commit hook #3214

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
aclark4life merged 2 commits into from
Nov 12, 2026
Merged

PYTHON-6263 Remove the blacken-docs pre-commit hook #3214

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
777d689
PYTHON-6263 Drop the blacken-docs pre-commit hook
aclark4life Nov 11, 2026
e2f15a8
Merge branch 'main' into PYTHON-6263
aclark4life Nov 12, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 0 additions & 7 deletions .pre-commit-config.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -51,13 +51,6 @@ repos:
always_run: true
pass_filenames: false

- repo: https://github.com/adamchainz/blacken-docs
rev: "1.20.0"
hooks:
- id: blacken-docs
additional_dependencies:
- black==22.3.0

- repo: https://github.com/pre-commit/pygrep-hooks
rev: "v1.10.0"
hooks:
Expand Down
2 changes: 0 additions & 2 deletions CODING-STANDARDS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,4 +1,3 @@
<!-- blacken-docs:off -->
# Intent

This document describes the common coding standards for all projects maintained by the Python Drivers team. These standards apply to all written code, comments, and docstrings, both human and machine-authored. Use these guidelines both when writing and reviewing code.
Expand Down Expand Up @@ -203,4 +202,3 @@ if TYPE_CHECKING:
2. A poor commit message: “2x speedup on inserts (if document \> 1MB).”
4. Extended messages longer than the one line summary are permitted, but are not encouraged as they are squashed during pull-request merge. They may contain periods.
5. Do not force-push to an open PR unless absolutely necessary.
<!-- blacken-docs:on -->
Loading