Default target repo when creating a Merge Request: "EDIT" origin is overwritten by fork-relationship

Hello, I don't know which version is affected because I'm not the hoste of the GitLab instance. It is salsa.debian.org

This is not a support question but a request to improve usability of GitLab. IMHO it currently doesn't behave the way a user would expect.

Steps to reproduce

  1. Use the web frontend only.
  2. Go to repo "backintime" of user "fantu".
  3. Fork from that repo to establish the "fork relationship" with "fantu".
  4. Go to repo "backintime" of user "jwm".
  5. Choose a file and do "EDIT".
  6. Modify the file in the web-frontend editor.
  7. Commit and Create "Merge Request".

Now you will see that the target of the Merge Request is fantu/backintime.

But as a user I would expect to have jwm/backintime as target of the MR because I did EDIT the file in the repo of jwm and not fantu.

Two options I see to improve the situation

  1. When EDIT a file in a not-owned repo use that repo as a default target of a MR and ignore (overwrite) the fork relationship.
  2. If you don't want 1. then minimally warn the user about that the target repo isn't the same repo that the EDIT was done on. "Warn" means using a big red bling bling message box.
Edited by 🤖 GitLab Bot 🤖