When a hotfix gets merged to master a resync process must be done to rebase develop branch. As per current implementation it's not possible due the fact of the operation is not supported because resync prefix won't be recognized as matching pattern.
By having resync as a branch prefix name the following scenarios must be covered
First scenario:
Previous version -> v1.2.3
Version after hotfix gets merged at master -> v1.2.4
Latest version at develop -> v1.2.3-alpha.1
Resyncing will “copy” master version and create a new tag -> v1.2.4-alpha.1
Second scenario
Previous version -> v1.2.3
Version after hotfix gets merged at master -> v1.2.4
Latest version at develop -> v1.5.5-alpha.1
Resyncing will bump build version -> v1.5.5-alpha.2
When a
hotfixgets merged tomastera resync process must be done to rebasedevelopbranch. As per current implementation it's not possible due the fact of the operation is not supported becauseresyncprefix won't be recognized as matching pattern.By having
resyncas a branch prefix name the following scenarios must be covered