Skip to content

Commit

Permalink
Merge pull request GitTools#1264 from cbuice/patch-1
Browse files Browse the repository at this point in the history
Nitpicky typo correction
  • Loading branch information
gep13 authored Jul 25, 2017
2 parents 29cb260 + f765783 commit c8332ef
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion docs/reference/intro-to-semver.md
Original file line number Diff line number Diff line change
Expand Up @@ -24,4 +24,4 @@ For a more complete explaination check out [semver.org](http://semver.org) which
## SemVer in GitVersion
GitVersion makes it easy to follow semantic versioning in your library by automatically calculating the next semantic version which your library/application is likely to use. In [GitFlow](https://www.atlassian.com/git/tutorials/comparing-workflows/gitflow-workflow/) the develop branch will bump the *minor* when master is tagged, while [GitHubFlow](https://guides.github.com/introduction/flow/) will bump the *patch*.

Because one side does not always fit all, GitVersion provides many [Variables](../more-info/variables.md) for you to use which contain different variations of the version. For example SemVer will be in the format `{major}.{minor}.{patch}-{tag}`, but `FullSemVer` will also include build metadata: `{major}.{minor}.{patch}-{tag}+{buildmetadata}`
Because one size does not always fit all, GitVersion provides many [Variables](../more-info/variables.md) for you to use which contain different variations of the version. For example SemVer will be in the format `{major}.{minor}.{patch}-{tag}`, but `FullSemVer` will also include build metadata: `{major}.{minor}.{patch}-{tag}+{buildmetadata}`

0 comments on commit c8332ef

Please sign in to comment.