There should be an option to create a branch via the web editor when editing an upstream project
Problem to solve
As a contributor, I want to be able to quickly edit some content and submit my merge request. Right now, if you follow the simplest workflow to do that, there's one little step at the end that makes a difference.
In particular, when editing an upstream project, there's no option to create a branch via the web editor. Naming your own branch is desirable in situations where a pipeline is based upon the branch name. In the case of docs, we only run the relevant tests, and for that there are some naming conventions that we follow.
This is a strange UX and I think we should resolve it.
Further details
Here's some steps to reproduce:
-
Go to a project you don't have push access to.
-
Find a file to edit.
-
Click on the edit button and GitLab will tell you to fork the project.
-
By clicking fork, GitLab forks the project in the background and notifies you about that.
-
At this point, you can see from the previous screenshot, that there's no option to create a branch, GitLab will create this for you.
Proposal
This mainly happens because even after you hit the fork button, you're still on the upstream project (to which you have no push access), and the target branch option is not shown. I would expect to:
-
Either redirected to my fork on the same file to edit it (this way I would be able to create the branch myself)
-
Or, display the option to create my own branch (like we display when you have push access to the repo)
