Skip to content

Use convention to derive a SemVer product version from a GitFlow based repository

License

Notifications You must be signed in to change notification settings

bdhess/GitVersion

 
 

Repository files navigation

Icon

The easy way to use semantic versioning (semver.org) with a Git.

GitVersion uses your git repository branching conventions to determine the current Semantic Version of your application. It supports GitFlow and the much simpler GitHubFlow and might work with others (let us know).

GitVersion in action!

README

You are seeing:

  • Pull requests being built as pre-release builds
  • A branch called release-1.0.0 producing beta v1 packages

Once a release is done, and you tag the commit which was released, the version will automatically be bumped. See our wiki for the rules and examples of how we increment the SemVer.

Usage:

GitVersion can be used in several ways

Examples

We have a bunch of examples in our Wiki, if something is missing, let us know! There are examples for GitHubFlow and GitFlow

Supported Variables

Because not everyone is the same, we give you a bunch of different variables which you can use in your builds to meet your requirements

Additional Links

Chat

Have questions? Come join in the chat room:

![Gitter](https://badges.gitter.im/Join Chat.svg)

Icon

Tree designed by David Chapman from The Noun Project

About

Use convention to derive a SemVer product version from a GitFlow based repository

Resources

License

Stars

Watchers

Forks

Packages

No packages published

Languages

  • C# 97.6%
  • Ruby 2.2%
  • Other 0.2%