You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
But the pre-commit docs don't recommend this. This causes different developers getting different versions of black depending on when they install pre-commit
One example of how this broke things is the recent change in the pyproject.toml target-version option from 'cpy27' to ['py27'] which broke for developers that installed the pre-commit hook later.
pre-commit assumes that the value of rev is an immutable ref (such as a tag or SHA) and will cache based on that. Using a branch name (or HEAD) for the value of rev is not supported and will only represent the state of that mutable ref at the time of hook installation (and will NOT update automatically).
The text was updated successfully, but these errors were encountered:
bk-equityzen
changed the title
.pre-commit-config README example not recommended by prec
.pre-commit-config README example not recommended by pre-commit
Mar 20, 2019
The readme recommends to use the following config:
But the pre-commit docs don't recommend this. This causes different developers getting different versions of black depending on when they install pre-commit
One example of how this broke things is the recent change in the
pyproject.toml
target-version option from'cpy27'
to['py27']
which broke for developers that installed the pre-commit hook later.From https://pre-commit.com/#using-the-latest-version-for-a-repository:
The text was updated successfully, but these errors were encountered: