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.

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.

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.

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.

yup its vitepress. I kind of got the idea of it from Husky. They also use vitepress too, so I thought why not?

For now I don't really tend to focus on that. But I have a bad habit of thinking 5, 10 years in advance. I have planned to add a biding feature in which advertisers will bid, and the highest biders, which would be top 20 biders or maybe more, will need to focus on that part, there ads would be displayed on the site, and of course for good measures, it would be 80% content and 20% ads, like this it's a win-win situation, where advertisers and users both are winning, except me and my company because advertisers will probably find an exploit to this idea. But that's for another month, not this month.

Lambda is still under development, the current version is more all for public feedback and testing if it can make a MVP. I would be seeing into all of that content moderation thing. Just that it will take time... or well a lot to be more precise, mainly because I am the only one working on it. Which is hard... really hard, especially if you use Typescript with Nextjs, or maybe again I just have skill issues.

I didn't know there already existed any. I will remove that first-ever part. Thanks for informing me.

Thanks for informing I will see into it. Which is a hard thing to do, naming stuff is that one thing devs can't do well... mostly me or just skill issue again

I didn't really focus much designing the login and signup page much. But if you would like you can always give me a feedback in the github discussion[https://github.com/ezpie1/lambda-official/discussions/catego...]