GitTools/GitVersion

From git log to SemVer in no time

View on GitHub ↗Jump to charts ↓Open shareable report →

Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 1 hour ago
Added to GitGenius on September 22nd, 2026
Created on August 27th, 2013
Open Issues & Pull Requests: 24 (+1)
GitHub issues: Enabled
Number of forks: 664
Total Stargazers: 3,145 (+1)
Total Subscribers: 52 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 11.1 hours
Mean response time: 24.5 days
90th percentile: 42.9 days
Tracked items: 206

How this project is maintained

About 18% of issues opened in the past year have never received a reply. Work labelled "improvement" is answered fastest, typically in about an hour, while "feature" waits about 5 days. 89% of issues opened in the past year have been closed, leaving a working backlog. Three people close 93% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 18
New in 7 days: 3
Closed in 7 days: 5
Avg open age: 565 days
Stale 30+ days: 2
Stale 90+ days: 0

Recent activity

Opened in 7 days: 2
Closed in 7 days: 2
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • needs triage (100)
  • stale (36)
  • feature (34)
  • improvement (27)
  • bug (25)
  • missing-steps-to-reproduce (16)
  • breaking change (13)
  • documentation (10)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

GitVersion is a tool that automatically derives semantic version numbers from your git repository history.

The tool solves the problem of maintaining consistent version numbers across a project without manual version bumps. It examines your git log and branch structure to calculate the next semantic version automatically. This approach eliminates the need to hardcode version numbers in files or rely on manual tagging disciplines. The tool works by analyzing commit history, branch names, and existing tags to determine what the current version should be according to semantic versioning rules.

GitVersion suits teams that want to decouple version management from code changes and maintain a single source of truth in git itself. It works well for projects using continuous integration pipelines where automated versioning reduces friction and human error. The tool is particularly valuable for libraries and packages where version numbers need to be consistent across multiple build and release stages. Projects already following semantic versioning conventions will integrate most naturally, though the tool can be configured to work with different branching strategies and version schemes.

The project shows sustained development activity with regular updates addressing user-reported issues and feature requests. Maintenance efforts focus on keeping the tool compatible with evolving .NET ecosystems and git workflows. The codebase receives contributions that expand configuration options and improve the accuracy of version calculation across different repository states. Development includes attention to documentation and examples that help users understand how the tool interprets their repository structure.