title: How to configure GitVersion for Release Flow?
body: <p>I am trying to configure GitVersion to work with the <a href="https://blogs.msdn.microsoft.com/devops/2018/04/19/release-flow-how-we-do-branching-on-the-vsts-team/" rel="nofollow noreferrer">Release Flow</a> branching strategy.</p>
  
  <p><a href="https://i.stack.imgur.com/a7CEV.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/a7CEV.png" alt="enter image description here"></a></p>
  
  <p>Basically, I have a mainline Master branch, Release, Feature and Fix branches. The Feature and Fix branches are created from the Master branch and merged back into Master via a pull request. At the end of a sprint, I create a Release branch from Master, which will last till the end of the next sprint, when a new Release branch will be created. The Release branches are not merged back into master. They can even be deleted after a new Release branch has been created. If there's a hotfix needed, it will be developed on a Fix branch created from and merged back into master and then cherry-picked into the current Release branch. I only use git tags for major releases.</p>
  
  <p>Going back to GitVersion, I want to configure it so that the minor version number will increase when I create a new release branch and the patch number to increase when there's a new commit on the release branch (cherry-picked from a Fix branch). </p>
  
  <p>Has anyone done that already and can help me?</p>