Minor documentation improvements about pre-commit.com HOT 5 CLOSED

• 721b6a1
• yes, that's probably a good idea
• Is the language that a hook is implemented in actually important? pre-commit is supposed to make that irrelevant
• It's not always .git/hooks/pre-commit (submodules, custom GIT_DIR, etc.). PRs welcome if you think you can improve the current verbiage though :)
• heh, neither is global exclude nor the new configuration format -- I've been meaning to add a section about that.
• I think merging them actually creates more confusion -- it also makes it difficult to differentiate between the current repository and a hook repository (is ./ os.getcwd()/... or hook-repo/...?).

from pre-commit.com.

Is the language that a hook is implemented in actually important? pre-commit is supposed to make that irrelevant

Yes I think it is, because:

• Docker based hooks require a Docker engine
• Go hooks require Go installed.
  Same for Ruby & Swift I guess, even if I never used them

For the rest, I don't want to pressure you, there's no hurry :)
I may send a PR to suggest some wording changes

from pre-commit.com.

Sweet, if you want to try and take a stab at the language bits, the code for that sits here and here.

from pre-commit.com.

Sure. You can assign this to me

from pre-commit.com.

I think this has been addressed -- thanks again!

from pre-commit.com.