Repository navigation
support hooks located in repository #367
Description
- repo: ./pre-commit-hooks
sha: ''
hooks:
- id: vault
Updating pre-commit-hooks...An unexpected error has occurred: CalledProcessError: Command: ('/usr/local/bin/git', 'clone', '--no-checkout', 'pre-commit-hooks', '/Users/gretel/.pre-commit/repoiXzY0j')
Return code: 128
Expected return code: 0
Output: (none)
Errors:
fatal: repository 'pre-commit-hooks' does not exist
Activity
asottile commentedon May 3, 2016
You'll need to use full paths: http://pre-commit.com/#developing-hooks-interactively
gretel commentedon May 3, 2016
this is why i was requesting to support
./style paths. it's kinda counterfeiting the concept of using git when pre-commit requires to have static paths in it's configuration, i'd say.asottile commentedon May 3, 2016
I think what you actually want to use is the (still undocumented unfortunately) local hooks:
#226
This lets you use the current repository to configure hooks.
The reason we can't really support relative paths is they need to refer to a universally accessible location (since hooks are cached). If we allowed relative paths, depending on cwd this could refer to a different location (and different hooks!). Local hooks aren't cached since they don't create an environment
gretel commentedon May 3, 2016
working fine now with repo-local script. may i suggest this example to have it less-undocumented:
asottile commentedon May 4, 2016
local hooks are now documented here: http://pre-commit.com/#repository-local-hooks
Merge pull request pre-commit#367 from pre-commit/all-repos_autofix_s…