You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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 therc
branch represents the accumulated sprint work. Occasionally we have an issue in prod that requires immediate resolution. In those cases, we branch frommaster
to develop the hotfix. After the hotfix is merged intomaster
, we need to merge those changes forward intorc
.I'm encountering an issue with the generated version when performing this merge forward from
master
torc
. 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?
The text was updated successfully, but these errors were encountered: