Merge request creation flow takes user to (wrong) existing MR instead of new MR template page
When using the "edit" feature on another project's code you are not a member of, GitLab creates a fork of the project in your space, commits the change to your fork, and tries to take you to a merge request page - but instead takes you to a different page.
Steps to reproduce
- Browse a project on GitLab.com (Screenshot 2)
- Browse to a project you are not a member of, and under Repository, browse to a particular file (Screenshot 3)
- Log in. (Screenshot 4 )
- Choose "Edit" (Screenshot 5)
- Make changes, enter comment. (Screenshot 6)
- Click "Commit changes"
- Being taken to a New Merge Request template for your changes
- (see Screenshot 9 for expected result)
- You are taken to a different user's merge request for the same project (Screenshot 7)
- You can still browse to the "Merge Requests" tab, and see the notice that you've pushed to a local patch, and are presented with a "Create Merge Request" button (Screenshot 8).
- Clicking this takes you to the page you'd expect (Screenshot 9)
Relevant logs and/or screenshots
(moved to inline links above)
Output of checks
This bug happens on GitLab.com
Check workflow followed when Edit File on repo-user-can't-commit-to page's "Commit changes" button is clicked.