Merge requests mistakenly target personal fork instead of upstream repo
merge requests mistakenly target personal fork instead of upstream repo
Steps to reproduce
- Create a personal fork of an upstream repo
- Push a new branch to your personal fork
- Go to your list of branches in your personal fork
- Click on the "Merge Request" button on the right of the row next to the branch from which you want to create your merge request
Example Project
What is the current bug behavior?
It will set the target to be the master branch of your personal fork, which is wrong. It should set the target to be the master branch of the upstream repo from which your repo was forked.
Note that if you visit your repo's main page soon enough after pushing to it, you will be presented with a notification that you recently pushed a branch and offered the option of creating a merge request from that branch right on your repo's home page. That method of creating a merge request still works as expected. It's only if you later go to your list of branches and create a merge request from that list that you will see this bug.
What is the expected correct behavior?
It should set the target to be the master branch of the upstream repo from which your repo was forked
Relevant logs and/or screenshots
This bug happens on GitLab.com
Output of checks
This bug happens on GitLab.com
Results of GitLab environment info
This bug happens on GitLab.com