Gabriel Nützi

@mjk-gh Thanks for the input! Guess what, I already thought about your proposed feature, but the points which @rycus86 already pointed out, have arised in my thoughts as well. A...

Ah, jeah it installs the templates into `/usr/share/git-core/templates/hooks` which is used by default by Git as template dir. My test 001 is failing now because I set `core.hooksPath=~/.githooks/templates` In some...

Ok, jeah no worries. Thanks for the explanations. I think it makes sense to have hook run-wrappers always available. I try :crossed_fingers: to just not put them into a "template"...

I agree. :-). See #85 : The thing is if we strong need a user input from ```shell MESSAGE="$(printf "%s\n%s" "$MESSAGE: $HOOK_PATH" " Do you accept the changes?")" show_prompt ACCEPT_CHANGES...

Default accepting should probably be disabled by default. And an opt-in feature. Especially in the new implementation. https://github.com/gabyx/githooks So any Git GUI will fail in the background because no prompt...

FYI: This is now implemented in the new version. See https://github.com/gabyx/githooks#user-prompts

Yes but we dont know which ones habe installes wrappers or is probably not so important we anyway search for a string inside the wrapper to be sure its rhe...

Jeah, thats a good point, but when we would have the triggered file in place, we are free what we could do: automatic migration or just tell the user, its...

i think we need to make sure that we dont accidentally execute githooks wrapper scripts again ;) if they are still in place accidentally, hmm but thats cumbersome to detect...

I was also thinking about having the whole githooks project in the way as `brew` works would be nice. We just clone this repo (so `install.sh` would only basically clone...