Description
I have the following branching strategy:
master -> rc -> feature branch
master -> hotfix
Nothing remarkable; master represents what's in prod. We work in sprints, so the rc branch represents the accumulated sprint work. Occasionally we have an issue in prod that requires immediate resolution. In those cases, we branch from master to develop the hotfix. After the hotfix is merged into master, we need to merge those changes forward into rc.
I'm encountering an issue with the generated version when performing this merge forward from master to rc. I expected the version to be a pre-release as the base is not the default branch but instead it's generating a full release version because the current branch is the default branch.
Any suggestions or is this something that should possibly be considered in the version generation code?