Repository navigation
Can't setup pre-commit integration; please cut new release #591
Description
Activity
@ngie-eign You right. I'm just using rev
masterinstead of specifying the versionReacted by Enji Cooper@edschofield Any news about releasing a new release?
As @ngie-eign wrote, current version doesn't work fine with pre-commit because of the missing hook file
user@host:~/Code/project $ pre-commit [INFO] Initializing environment for https://github.com/PythonCharmers/python-future. An error has occurred: InvalidManifestError: =====> /home/user/.cache/pre-commit/repo6ec7nce2/.pre-commit-hooks.yaml is not a file
pre-commitrequires a revision in order to function and given that.pre-commit-hooks.yamlwas added after the last release, end-users can't use the pre-commit integration provided in commit a9c6a37 without specifying an explicit git hash.While a git hash would suffice for
rev, I would really appreciate an official release be cut so folks can rely on that version for integration, instead of a random version offmaster, as the quality of that version is unknown.Thanks!