Husky.Net VS husky

I use Husky.net to hook in dotnet format on changed files.

One suggestion that I have is to set up Husky.Net. It'll allow you to ensure that dotnet format is run on every staged file. Assuming you guys are doing appropriately sized commits and PRs, your team will be able to evaluate formatting changes better by reviewing them in chunks as they come in, and not all at once in a large codebase.

https://github.com/alirezanet/Husky.Net to auto run csharpier or anything else as a pre-commit hook

Pre-commit hooks could work for this, but you will have to ensure everyone sets up the same pre-commit hook. https://github.com/typicode/husky or https://github.com/alirezanet/Husky.Net can make that easier.

Reading Biome doc I also switched from husky to lefthook.

Dive deeper into the world of Husky with the official documentation. Explore the capabilities of Standard Version through its comprehensive documentation. Unravel the mysteries of semantic-release with its detailed documentation. Discover the versatility of bumpp with its comprehensive documentation.

Let’s walk through the steps for a one-time setup to configure husky pre-commit and pre-push hooks, ESLint with code styles conventions, prettier code formatter, and lint-staged. Husky automatically runs a script on each commit or push. This is useful for linting files to enforce code styles that keeps the entire code base following conventions.

We were already using lint-staged and have a pre-commit hook in place using Husky in our project for linter and prettier. So it made sense to add a check here.

Now, let's talk about Husky. It's a wonderful tool that enables you to run scripts on any Git hooks. We'll add a pre-commit hook to run ESLint and Stylelint checks before committing. This ensures that we don't commit code with errors.

In all my projects I use husky, lint-staged and commitlint.