Option to not merge to master for release-finish

[ismarslomic]

Hi, thanks for great plugin!

Is it possible to do the merge, for goal release-finish, only to development (develop), but not production (master)? We don´t want to merge an release to master branch which is not yet tested (performance test, manual tests, etc) in an test environment. In addition we do not allow push to master without Pull Requests.

Since release-finish goal automatically merge to develop and master, after creating an release, it is difficult to achieve this.

Any suggestions?

[aleksandr-m]

Looks same as #97. Why not to use git merge? Also if it not a release branch really, then why not to call it a feature branch?

[ismarslomic]

Good point! The only advantage of using release branch is because we do actually releases from this branch and we also get auto-merge feature to develop-branch within Atlassian Bitbucket, when we create Pull Requests to merge from bugfix -> release branch

[hypery2k]

having the same issue here. Any new thoughts here?

[aleksandr-m]

@hypery2k Do you really need a release branch? Feature/support/hotfix/some other branch maybe?

BTW the hotfix-finish goal has skipMergeProdBranch option since 1.12.0.

[hypery2k]

I'm using the option for now, so from my side no need for the issue as it can be resolved with the help of the option

[aleksandr-m]

Duplicate of #74, which is resolved by now.