Husky.Net VS LibGit2Sharp

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.

To use it as an API on windows you might want to go with a C# wrapper. libgit2sharp

You might want to leverage something like libgit2 if you store that data in a unique location. After you commit changes to your data, you can find the patch differences in the file. Then store the commit hash and set up communication that wakes up when the hash changes. When the commit hash changes, you send just the patch changes to the clients which can apply them to their local copy.

libgit2sharp to work with git repositories in .NET https://github.com/libgit2/libgit2sharp

Is it something you could possibly achieve with git? - https://github.com/libgit2/libgit2sharp/

Currently, my plan is to use LibGit2Sharp to do almost all the logic, and use System.IO to manage the local files. Problem is: LibGit2Sharp documentation is very sparse and hard to read.