Live data from Hacker News

Show HN: GetHooky – a language-agnostic Git hook manager

ezpieco.github.io

21–23 of 23 posts

Re: Show HN: GetHooky – a language-agnostic Git hook manager

#21
post #20

Earlier quoted context omitted.

Unfortunately —-no-verify is all or nothing. If I have 10 hooks and only want to skip one of them it won’t do the job

maybe git should fix this. Or maybe I could fix this internally in githooky maybe? I don't know, but I could give it a try, at least. How would you like the approach to be? Any ideas, I'll take it.

A naïve stab at the UX is to exclude the name of the hook(s) you want to skip in the command line via a flag. Then you can also provide a configuration that will skip it in a file as well that the command line option overrides - good for people who want to skip for longer periods and don't want to type it out.

Re: Show HN: GetHooky – a language-agnostic Git hook manager

#22

Why would someone use this tool when `pre-commit` exists? 14k stars on GitHub: > multi-language package manager for pre-commit hooks I'm all for having options, I'm just curious at what GetHooky brings to the table.

Quit simple. To use pre-commit you would need python installed, and to be honest, not everyone is going to install python just to install pre-commit right? Meanwhile GetHooky being a CLI tool just requires you to install the respective binary for your system, and done.

Also, pre-commit's approach of creating a YAML file and then running your pre-commit hook is a bit overengineering, in my opinion. I mean, what if I just want to run pytest? A whole YAML file sounds a bit unnecessary work to me. But with GetHooky, it's simple. Just use the add command and then the install command, and your job is done. Nothing much complicated.

Hope this helped you clarify what exactly GetHooky is, its not a package that requires you to install a language for its runtime, its a CLI tool, just download the binary and done.

Re: Show HN: GetHooky – a language-agnostic Git hook manager

#23
post #20

Earlier quoted context omitted.

maybe git should fix this. Or maybe I could fix this internally in githooky maybe? I don't know, but I could give it a try, at least. How would you like the approach to be? Any ideas, I'll take it.

A naïve stab at the UX is to exclude the name of the hook(s) you want to skip in the command line via a flag. Then you can also provide a configuration that will skip it in a file as well that the command line option overrides - good for people who want to skip for longer periods and don't want to type it out.

Honestly, I like the idea. I'll add it in a later release, but if you want you can also do a PR on github https://github.com/ezpieco/gethooky

I have no issues in accepting PRs it would be cool to see how you can cook this up.

Post reply on HN