docs: update pre-commit exclude and force-exclude explanation #4898
+51
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR improves the documentation for how Black handles exclude patterns when
used with pre-commit. Since pre-commit passes file paths directly to Black,
Black's normal exclude rules do not apply unless --force-exclude is used.
The updated section explains:
why pre-commit's own exclude should be preferred,
how exclusions can be configured in pyproject.toml,
when --force-exclude is helpful as a fallback.
Closes Document using pre-commit and how --force-exclude can help #3015