Confusion by GitLab-Flow from 8.5 version

Hi there, according to GitLab-Flow document: https://about.gitlab.com/2014/09/29/gitlab-flow/ in the section Production branch with GitLab flow it should be possible to have a default( master ) branch AND a special production branch for the final code. In this case user should be able to checkout the default master branch, commit his work there, and then make a merge-request to the production branch. This works actually fine, but since GitLab-8.5 as soon as I am merging into production branch (which is not the default one) - GitLab displays a blue button message like: You pushed to production branch - make merge request. It suggest me to merge into default branch back.

This is very confusing, and this behavior assumes the typical GitHub-Flow.. one default master(which is a production one) branch and several feature/development branches.

So I think, in order to support the special GitLab-Flow, with an ability to have final production branch separate from default branch, this behavior should be changed. Maybe there should be just a setting to remove this blue-messages-button. Or a setting to specify non-default branches as production branches... and then GitLab suggest to merge into this production branch.. What do you think about this?