Fork relationship is not respected for certain projects
This was fixed in GitLab Versions 14.10 and 15.0
Community contributors have reported that they are unable to submit merge requests to https://gitlab.com/gitlab-org/ci-cd/custom-executor-drivers/fargate. Creating a new merge request will target master on the forked project instead of the upstream project, even if the upstream project is explicitly selected as the target.
Interestingly, I cannot reproduce this when logged in as
bwill. However, I can reproduce it if I create a new account on GitLab.com. I suspect that this is only reproducible by users who are not members of
Steps to reproduce
- Login as a user who is not a member of
- Go to https://gitlab.com/gitlab-org/ci-cd/custom-executor-drivers/fargate and click the
- Make a change in your project and commit it to a new branch
- Go to https://gitlab.com/<your_project_path>/-/merge_requests/new?merge_request%5Bsource_branch%5D=<your_branch_name>, or create a merge request from your branch using and of the
Create merge requestbuttons
- Observe that your merge requests targets
masterof the current project instead of the upstream project
- Attempting to use
Change branchesdoes not allow you to target the upstream project
What is the current bug behavior?
/-/merge_requests/new ignores the
merge_request[target_project_id] parameter and still targets the current project
What is the expected correct behavior?
/-/merge_requests/new should respect the fork relationship and target the upstream project
Output of checks
This bug happens on gitlab.com
Issue most likely lies in