<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=362380) </details> <!--IssueSummary end--> From an issue, there is a button called `Create merge request`:  I think there are several reasons why this is confusing: - The button label, `Create merge request`, does not really correspond to the action you see when you expand the drop-down, which is `Create merge request and branch`. That is very different! (see next point) - I found that most of our developers fell in the same trap: seeing just `Create merge request`, they think this will help them create a MR for **an existing branch** previously created for this issue. That's fair. Why would you expect anything different from `Create merge request`? What happens instead when they click that button is that they end up with a new empty branch for their MR, which they will have to cancel when they figure out what happened. - Why is the default for this button `Create merge request` (which actually means `Create merge request and branch`) and not `Create branch`? Wouldn't that be the more logical workflow? Isn't it more common to create a branch and only later decide whether it deserves a MR or not? How often does one want to create a MR as a "promise", for a branch that doesn't even exist yet? - Same reasoning: `Create merge request and branch` sounds odd to me. Why would the MR come before the branch? GitLab14.10.2-ee