What's the documentation site using and theme? Really like the look.
Show HN: GetHooky – a language-agnostic Git hook manager
11–20 of 23 posts
Re: Show HN: GetHooky – a language-agnostic Git hook manager
#12What's the documentation site using and theme? Really like the look.
Since it’s hosted on GitHub, I snooped through the repo, and it appears to be created using VitePress [1].
[1] https://vitepress.dev/
Re: Show HN: GetHooky – a language-agnostic Git hook manager
#13Earlier quoted context omitted.
There are dozens of your type out there that I don’t understand. The “I don’t want no commit hooks running on my machine. I and only I control what happens on my local machine” purists. There’s at least one in every job I work. If the thing is going to block in ci anyway, why are you opting for a push and pray approach? Why arbitrarily increase your feedback loop time and add waiting time for each loop in ci? Chances…
Valid questions. For me it's two things: 1) sometimes hooks are configured on commit, and I prefer to have a very quick and lightweight commit action. If I'm changing branches sometimes I'll commit WIP changes so I can easily come back to it later. I know git stash accomplishes a very similar functionality but it's just a preferred workflow. 2) I don't like the feedback I get from git hooks when committing in the VS…
Yeah it seems a lot of this boils down to the myriad of ways people use git. I can imagine some ways are easier than others when using hooks. And githooks are “all or nothing” without an easy way to enable/disable them per hook - which I believe is one of the problems that OP aims to solve.
Re: Show HN: GetHooky – a language-agnostic Git hook manager
#14What's the documentation site using and theme? Really like the look.
Since it’s hosted on GitHub, I snooped through the repo, and it appears to be created using VitePress [1]. [1] https://vitepress.dev/
yup its vitepress. I kind of got the idea of it from Husky. They also use vitepress too, so I thought why not?
Re: Show HN: GetHooky – a language-agnostic Git hook manager
#15Now thanks to Go and Rust, every single tool that are recommended to be installed in developers computers and server are required to be "sh -c "$(curl -fsSL " installed... We are so cooked...
well you don't really have to you can just install the binary from the release page in github, but I mean, then mv it to the required location in order for it to work globally. So I thought why not just create a bash script for that.
Re: Show HN: GetHooky – a language-agnostic Git hook manager
#16Earlier quoted context omitted.
There are dozens of your type out there that I don’t understand. The “I don’t want no commit hooks running on my machine. I and only I control what happens on my local machine” purists. There’s at least one in every job I work. If the thing is going to block in ci anyway, why are you opting for a push and pray approach? Why arbitrarily increase your feedback loop time and add waiting time for each loop in ci? Chances…
Valid questions. For me it's two things: 1) sometimes hooks are configured on commit, and I prefer to have a very quick and lightweight commit action. If I'm changing branches sometimes I'll commit WIP changes so I can easily come back to it later. I know git stash accomplishes a very similar functionality but it's just a preferred workflow. 2) I don't like the feedback I get from git hooks when committing in the VS…
I can totally understand the point you're making there. I used to use VScode too few years ago, but now I use vim most of the time. So majority of the time I'm in my terminal so if the hook fails for me, it gives me the error, and I have zero problems with that. So I get what you mean there, but I mean, for those who live in their terminals git hooks kind of make sense, I mean after all, we see the error cause its the terminal after all.
So yeah it just boils down to the fact how you would use git, in vscode, hooks aren't great, cause its not going to display the error, but if you use the terminal, even in vscode, you'll see the error getting displayed on the terminal.
Re: Show HN: GetHooky – a language-agnostic Git hook manager
#17Earlier quoted context omitted.
There are dozens of your type out there that I don’t understand. The “I don’t want no commit hooks running on my machine. I and only I control what happens on my local machine” purists. There’s at least one in every job I work. If the thing is going to block in ci anyway, why are you opting for a push and pray approach? Why arbitrarily increase your feedback loop time and add waiting time for each loop in ci? Chances…
Valid questions. For me it's two things: 1) sometimes hooks are configured on commit, and I prefer to have a very quick and lightweight commit action. If I'm changing branches sometimes I'll commit WIP changes so I can easily come back to it later. I know git stash accomplishes a very similar functionality but it's just a preferred workflow. 2) I don't like the feedback I get from git hooks when committing in the VS…
1) You can pass `--no-verify` to `git commit` and it will skip the hooks. An alias would make it even more ergonomic.
2) You can write hooks that make the changes for you where possible. This is what I do for lints from auto-formatters. Don't know how to handle the rest of your VS Code issues though.
Re: Show HN: GetHooky – a language-agnostic Git hook manager
#18Why 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.
Re: Show HN: GetHooky – a language-agnostic Git hook manager
#19Earlier quoted context omitted.
Valid questions. For me it's two things: 1) sometimes hooks are configured on commit, and I prefer to have a very quick and lightweight commit action. If I'm changing branches sometimes I'll commit WIP changes so I can easily come back to it later. I know git stash accomplishes a very similar functionality but it's just a preferred workflow. 2) I don't like the feedback I get from git hooks when committing in the VS…
1) You can pass `--no-verify` to `git commit` and it will skip the hooks. An alias would make it even more ergonomic. 2) You can write hooks that make the changes for you where possible. This is what I do for lints from auto-formatters. Don't know how to handle the rest of your VS Code issues though.
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
Re: Show HN: GetHooky – a language-agnostic Git hook manager
#20Earlier quoted context omitted.
1) You can pass `--no-verify` to `git commit` and it will skip the hooks. An alias would make it even more ergonomic. 2) You can write hooks that make the changes for you where possible. This is what I do for lints from auto-formatters. Don't know how to handle the rest of your VS Code issues though.
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.