3 ms·
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 chan
by jmholla 1y ago
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.
- SOLAR_FIELDS 1y agoUnfortunately —-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
- Ezpie 1y agomaybe 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.
- SOLAR_FIELDS 1y agoA 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.
- Ezpie 1y agoHonestly, 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 https://github.com/ezpieco/gethooky I have no issues in accepting PRs it would be cool to see how you can cook this up.