I am running GitVersion with GitFlow in Continuous Deployment mode with practically all default settings.
This is my GitVersion.yaml:
mode: ContinuousDeployment
continuous-delivery-fallback-tag: ''
branches:
master:
tracks-release-branches: true
merge-message-formats: {}
ignore:
sha: []
These are the steps I am taking:
- Create tag named
1.0.0on themasterbranch - Create the
developbranch off of master (GitVersion shows this as 1.1.0, which is great, this is what I want) - Create the
feature/myfeaturebranch off ofdevelop - Create a commit to
feature/myfeature - Pull request from
feature/myfeature -> develop - At this point we are at
1.1.0, and this makes complete sense to me. - Create the
releasebranch off ofdevelop - If I run GitVersion, I am still at
1.1.0, again, this makes sense to me. - Pull request from
release -> master - Master now shows the version is
1.0.1. Why is GitVersion not recognizing the history that I just pulled from thereleasebranch?
The only thing that I can do to solve the issue is to manually generate a tag on my release branch, which GitVersion will then use to determine the next version. I do not want to create the tag until I pull into master, at which point I will generate a new build and set a tag on my master branch automatically via my pipelines in Azure.