No support for arm64 unfortunately :( OP, I tried installing via rosetta on macOS arm:
arch -x86_64 sh -c "$(curl -fsSL https://raw.githubusercontent.com/ezpieco/gethooky/master/tools/install.sh)"
And I get the following error:
mv: fastcopy: open() failed (to): /usr/bin/hooky: Operation not permitted
I curl'd and installed the x86 version manually into my ~/.zsh_scripts folder to get past this; I think for darwin clients you need to install to /usr/local/bin to get past perms errors (maybe just for arm macs?).
ericyd · 11h ago
There's always a spectrum of preference with these things. Personally I don't like git hooks for my workflows because I know CI will enforce the relevant checks. In addition, I am fine running an extra test or lint or build command before opening my PR to verify it works locally. Git hooks are a nice solution but for me they just slow down common operations so I'd rather not use them. This tool looks like a nice improvement over project-level configurations like Husky (in the npm space) because it's an individual configuration so I could just skip it, whereas husky gets configured for everyone.
SOLAR_FIELDS · 9h ago
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 are the time to get feedback is at least a couple orders of magnitude faster locally, you’re paying not only the startup time to register the runner and bring it online, get dependencies installed etc but also the manual time to context switch to the CI window etc. Just do all your linting and auto formatting and whatever on commit. It’s all work you’re going to have to do anyway, why introduce some extra less efficient step on yourself to slow yourself down?
ericyd · 8h ago
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 Code interface. For example, we have a "lint" hook that runs on pre-push. When it fails, I have to run "lint" manually in my terminal anyway to actually see the errors, because VS Code doesn't show me the actual errors. I believe the hook results are available in some other tab or something but I haven't bothered to learn it.
Both of these are just personal preferences, and maybe a little bit of resistance to learning new workflows. I don't consider myself a purist about it and I've never argued about it at work but hopefully this sheds a little light on my perspective.
Edit: regarding the "push and pray" approach, I personally don't do that, I'll run it locally first, I just prefer to run it myself rather than via a hook.
Using git hooks directly almost always leaves you maintaining a small collection of bash scripts for installs, upgrades, config in the long run. Personally I'm fine with that but tooling can be nice, no?
(in case it's not clear though these tools are wrappers - under the hood it's still git hooks like you linked)
robertlagrant · 16h ago
It's a git hook manager.
nodesocket · 4h ago
What's the documentation site using and theme? Really like the look.
sjoedev · 3h ago
Since it’s hosted on GitHub, I snooped through the repo, and it appears to be created using VitePress [1].
[1] https://vitepress.dev/
greatgib · 5h ago
Now 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...
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 are the time to get feedback is at least a couple orders of magnitude faster locally, you’re paying not only the startup time to register the runner and bring it online, get dependencies installed etc but also the manual time to context switch to the CI window etc. Just do all your linting and auto formatting and whatever on commit. It’s all work you’re going to have to do anyway, why introduce some extra less efficient step on yourself to slow yourself down?
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 Code interface. For example, we have a "lint" hook that runs on pre-push. When it fails, I have to run "lint" manually in my terminal anyway to actually see the errors, because VS Code doesn't show me the actual errors. I believe the hook results are available in some other tab or something but I haven't bothered to learn it.
Both of these are just personal preferences, and maybe a little bit of resistance to learning new workflows. I don't consider myself a purist about it and I've never argued about it at work but hopefully this sheds a little light on my perspective.
Edit: regarding the "push and pray" approach, I personally don't do that, I'll run it locally first, I just prefer to run it myself rather than via a hook.
(in case it's not clear though these tools are wrappers - under the hood it's still git hooks like you linked)
We are so cooked...