GitTools/GitVersion

Health v2 · maintenance only

Adoption not part of the score

3145 stars · 660 forks observed · 2026-08-28

What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded

GitVersion is a tool that calculates a Semantic Version (SemVer) number for a commit by analyzing a repository's Git history and branching strategy. It can be consumed as a CLI, .NET tool, MSBuild task, NuGet library, Docker container, or CI pipeline task to stamp versions on builds and artifacts.

Use cases

• generate semantic version numbers from git history
• version nuget packages automatically in CI
• calculate semver from gitflow or github flow branches
• patch assemblyinfo.cs with version numbers during build
• integrate versioning into github actions or azure devops pipelines
• stamp build artifacts with version numbers on a build server
• run versioning in docker containers in ci pipelines

When to choose

• you need automatic SemVer generation driven by git history and branching conventions
• you build .NET projects and want assembly version patching via MSBuild
• you use CI servers like GitHub Actions, Azure DevOps, GitLab CI, or Jenkins and need version variables in the pipeline
• you follow GitFlow or GitHub Flow and want pre-release versions for PRs and release branches

When to avoid

• your project does not use git or does not follow any recognizable branching strategy
• you need a fully supported stable library API - the NuGet library option is explicitly unsupported and may break between releases
• you use a simple fixed version number scheme unrelated to git history

Facets

cli-tool · maturity stable

build-tool developer-tools ci-cd version-control developer-tools version-control cross-platform cli dotnet windows semver versioning git dotnet msbuild continuous-integration assembly-versioning devops docker linux macos

Member repositories

For agents

markdown · JSON · MCP: product_card(name="GitTools/GitVersion")