<!--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=472679) </details> <!--IssueSummary end--> # Context When visiting a branch in a private repository that is a fork of another project and using the "Create merge request" button, the default target branch is the public repository. While there is a warning that highlights it targets the public repository:  This can be overlooked easily. # Steps to reproduce 1. Fork a public project into a private repository 2. Create a new branch and make some changes 3. Go to the Web UI on the branch you created 4. Click "Create a merge request" 5. Observe it targets the public repository branch by default # Proposed change It would be great if the default was to target the main branch of the _private_ repository, with the option to change it to the public one as needed. This would be a more secure-by-default design.