make "git flow release" tag master

[JasonWoof]

git flow release was tagging the last commit in the release branch instead
of master.

This commit makes it tag master (after the merge) instead.

I believe this commit restores the original and intended behavior, which
appears to be changed (probably unintentionally) in commit afb191f.

[jasmarc]

+1 I'd like to see this implemented as well. Is there a more formal way of +1ing this?

Was this really the original behavior? Because it's what I expected and was disappointed to find out it's not the current behavior.

[SparK-Cruz]

+1
I want this working too.

[mmcgahan]

+1

[ByFe]

+1

[cherrydev]

+1

[adben]

+1

[petervanderdoes]

This is implemented in my fork git-flow (AVH Edition)
My fork has diverged to much to make this into a pull request for nvie's gitflow,

Checkout the changelog for more information about bugfixes and new features implemented in my fork.

[cherrydev]

Is there some way we could get @nvie to comment on if this current behaviour is intended or if this is a bug?

[jnardone]

Agreed. This needs attention; it breaks our current workflow to use versions based on this. :(

[kaimi]

👍

[micky2be]

👍

[kamilchm]

👍

[jawshooah]

Dudes, this repo is pretty much dead in the water (latest commit was in 2012). If you're looking for active maintenance, check out @petervanderdoes's fork. It heals what ails you.

[ghost]

@jawshooah