Husky.Net VS EditorConfig

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.

Someone already went through the trouble of producing a editorconfig dotfile that conforms to the StyleCop rules, and yet it isn't even suggested to be applied by any important C# tool. Which is a glaring oversight as bad as when default gitignore files were not suggested by default, leading to countless repos cluttered with bin and obj folders.

Like this: editorconfig ?

Also https://github.com/RehanSaeed/EditorConfig as a starting point for enforcing C# rules and fixes like eslint.

Yes. This one is kept up to date as they add new rules to Visual Studio, it's my go-to to use as a base. It goes off of the Microsoft/.net guidelines and sprinkles stylecop style rules on top of it: https://github.com/RehanSaeed/EditorConfig