Does GitversionTask require manually tagging commits on the master branch? Would this typically be done on the build server that completes the pull request?
When we have master on 1.1.4 and then merge a release branch 1.2.0-FeatureA, I'd expect master to then be on 1.2.0. However, without a manual tag, according to gitversion it is on 1.1.5. Presumably, gitversion cannot distinguish if this commit came from a hotfix pull request or a release pull request. I'm not sure if I understand the philosophy of gitversion.
Ideally, all semantic versioning should be done by GitversionTask. And if necessary, we would have the possibility to bump the major. Every commit on the master branch should have unique SemVer.
- We are using gitflow
- We are using the default config (no Gitversion.yml file)
- We are working with devops
- https://github.com/GitTools/GitVersion
- Installed version 5.3.7
