<!--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> - [Work on this issue](https://contributors.gitlab.com/manage-issue?action=work&projectId=278964&issueIid=560985) - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=560985) </details> <!--IssueSummary end--> # Context In https://gitlab.com/gitlab-org/gitlab/-/issues/518021, the branch selector was updated to allow users to: * View the default branch at the top of the list * Allow users to quickly copy the ref name * More easily view long branch names with a longer branch selector width The design solution resolved https://gitlab.com/gitlab-org/gitlab/-/issues/518021, https://gitlab.com/gitlab-org/gitlab/-/issues/346777, and https://gitlab.com/gitlab-org/gitlab/-/issues/438154. This updated branch selector has not yet been percolated to the flow when users create a new merge request. | Current MR branch selector in new MR flow | New Source Code branch selector | |-------------------------------------------|---------------------------------| | {width="1004" height="564"} | {width="1005" height="623"} | > @nickleonard > > this is in the MR creation flow but I don't know which in this project is the default branch — there's main and master  > > {width="216" height="240"} # Design proposal In the MR creation flow (`Create merge request` \> `Change branches` \> `Select Source or Target branch selector`): * Use the new branch selector component implemented in https://gitlab.com/gitlab-org/gitlab/-/issues/518021 * If needed, make sure the `default` label appears on the default branch. I suspect this will be resolved if we use the correct component.