From f765783f733bc51f4c90dee2f1f47ac3d650623e Mon Sep 17 00:00:00 2001 From: Curtis Buice Date: Tue, 25 Jul 2017 14:16:48 -0400 Subject: [PATCH] Nitpicky typo correction --- docs/reference/intro-to-semver.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/reference/intro-to-semver.md b/docs/reference/intro-to-semver.md index ccbfc252d5..262b97cd01 100644 --- a/docs/reference/intro-to-semver.md +++ b/docs/reference/intro-to-semver.md @@ -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}`