Validate that branch names follow GitFlow about gitversion HOT 4 CLOSED

@nulltoken I belive your pull fixed this?

from gitversion.

@andreasohlund I'm not sure to understand what we're trying to avoid here.

The merge commit that is referred to seems to bear a message containing a valid release branch name (ie. starts with release- or release/).

I may be missing something obvious...

from gitversion.

Release-4.1.1 is not valid since releases never increment patch version.

In this case the branch should have been called hotfix-4.1.1

Sent from my iPhone

On 27 nov 2013, at 11:36, nulltoken [email protected] wrote:

@andreasohlund I'm not sure to understand what we're trying to avoid here.

The merge commit that is referred to seems to bear a message containing a valid release branch name (ie. starts with release- or release/).

I may be missing something obvious...

—
Reply to this email directly or view it on GitHub.

from gitversion.

Thanks for the information. I did miss something obvious.

I'll try to work something out. Either a passing test to demonstrate that this is fixed, or a failing test and a fix proposal.

from gitversion.