Release-finish merge is merging release-branch into develop instead of master onto develop

[pennajenna]

gitflow-maven-plugin/src/main/java/com/amashchenko/maven/plugin/gitflow/GitFlowReleaseFinishMojo.java

Line 308 in da562a0

gitMerge(releaseBranch, releaseRebase, releaseMergeNoFF, false,

When using this, the release-finish is merging release-branch onto master and tagging correctly. Then it merges release-branch onto develop. This doesn't allow for the tag to be on develop. Is there a reason for this?

[aleksandr-m]

@pennajenna Seems same as #213. Can you elaborate what benefit does it bring?

[pennajenna]

Yes, if you merge master into develop, the tag from master is on develop. The way it is now, develop doesn’t have the same tag

…

Sent from my iPhone

On Apr 21, 2021, at 3:16 PM, Aleksandr Mashchenko ***@***.***> wrote:  @pennajenna Seems same as #213. Can you elaborate what benefit does it bring? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.

[pennajenna]

#213 reasons are exactly the same as mine, having that tag on develop is a necessity for me Jenna

…

Sent from my iPhone

On Apr 21, 2021, at 4:20 PM, Jenna McCormick ***@***.***> wrote: Yes, if you merge master into develop, the tag from master is on develop. The way it is now, develop doesn’t have the same tag Sent from my iPhone >> On Apr 21, 2021, at 3:16 PM, Aleksandr Mashchenko ***@***.***> wrote: >> >  > @pennajenna Seems same as #213. Can you elaborate what benefit does it bring? > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub, or unsubscribe.

[pennajenna]

submitted a PR for this: #291

[pennajenna]

DUPLICATE of #213