PEP 385: add a note about client-side whitespace hooks (thanks georg.brandl).
This commit is contained in:
parent
90c17bffed
commit
cd4c9bb14d
|
@ -148,8 +148,11 @@ developed and deployed. The following hooks are being used:
|
||||||
|
|
||||||
* check whitespace: a hook to reject commits in case the whitespace doesn't
|
* check whitespace: a hook to reject commits in case the whitespace doesn't
|
||||||
match the rules for the Python codebase. Should be straightforward to
|
match the rules for the Python codebase. Should be straightforward to
|
||||||
re-implement from the current version. Open issue: do we check only the tip
|
re-implement from the current version. We can also offer a whitespace hook
|
||||||
after each push, or do we check every commit in a changegroup?
|
for use with client-side repositories that people can use; it could either
|
||||||
|
warn about whitespace issues and/or truncate trailing whitespace from changed
|
||||||
|
lines. Open issue: do we check only the tip after each push, or do we check
|
||||||
|
every commit in a changegroup?
|
||||||
|
|
||||||
* commit mails: we can leverage the notify extension for this
|
* commit mails: we can leverage the notify extension for this
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue