"Pull project code" and "Create new merge request" should be the same permission.
Created by: joehillen
"Pull project code" and "Create new merge request" should be the same permissions.
There seems to be a gap in reasoning about permissions.
Why can a user fork a project but then not open a merge request for that project? What is the use forking if you can't contribute back? What is the use of merge requests if you already have commit access?
I've found myself in this position several times. There is an existing project, and I haven't been given commit access to that project yet (usually because of an admin oversight). I want to make a simple change and ask the owner to merge it. I don't necessarily need or want commit access to do this, since the owner can review and merge my patch for me. I fork the project, push the changes to my fork, but then I can't open a merge request.
One solution would be to allow merge requests for "Reporters" but I propose a simpler solution.
Forking doesn't makes sense without merge requests, and merge requests don't make sense without forking; they should be the same permission.