GitVersion VS LibGit2Sharp

Gitversion: It reads your commit history and generates a semver version out of it. Say you are compiling main branch and have a tag 1.0. Then, you squash 3 PRs. When you build this version, the new version number will be 1.0.3. You can configure it to be smarter about increasing major, minor, patch fields. I typically use prefix on the commit messages so that it generates versions correctly. See more at https://gitversion.net/docs/

GitVersion is not available by default and needs to be installed beforehand if we want to use the features it offers. The action is available here.

Check this out https://gitversion.net/docs/

At work we use https://gitversion.net/docs/ in our devops pipelines. Similaf to git-semver it generates a version based on what's published previously.

Under Linux I use gitflow and gitversion. The former helps me with branch and tags management, the latter keep tracks of the semantic version in a semi-automatic fashion (given a branch/commit/tag it generate a semver automatically based on the repo log). Gitflow should be supported by GUI tools too, but I'm more a CLI guy.

I’m not sure about in Bitbucket, but our pipeline has installed GitVersion which ups the build version based on SemVer. https://gitversion.net/docs/ We have a HealthCheck endpoint to return this version.

I know that GitVersion exists, which I think can automatically calculate the version number for me. But it's not entirely clear to me that it will do this. Also it doesn't seem to have a nbgv set-version equivalent that will just create a tag based on the calculated version number.

Kind of like you mention though, I tend to still create a build script using gitversion then just have the GitHub Action kick off the script. I find value in being able to create artifacts on a developer machine so having a simple script to run makes that as painless as possible and when I last looked a year or so ago there wasn't a good way of running GitHub Actions on your development machine.

Self promotion: I made Verlite for this purpose, tho something like GitVersion might be more suitable for your workflow.

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.