Description
it would be nice if this repo would be configurable without touching the worktree. i use this repo extensively in my local work environments, where it's kind of annoying to have a "dirty" tree, especially since i like to send my contributions back here. ;)
typically, git hooks would consult the configuration stored in git-config, for example... is that something that would be accepted as a patch? maybe as an override to the config file?
this would also allow different people with different policies to use the same code more easily. the canonical example for me is #9, where we have more ... relaxed documentation policies (because of an old codebase).
in fact, now that i think of it, this would make it possible to have per-repository (say you're not in a monorepo) policies, while using the same hook repository everywhere...