WebIDE without Merge-Requests enabled shouldn't suggest on edits on default branch commit to new branch
Problem to solve
The Web-IDE suggests edits on the default branch target a new branch. This makes sense, when you have merge requests enabled. If you don`t - your users want to edit files on a branch and the edit goes to a -username- branch. This is confusing for our users.
When working on non default branches the edit "stays" on that branch.
Intended users
Personas are described at https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/ -->
Further details
Proposal
When Merge Requests are disabled all edits should go to the current branch - even on the default branch.
Permissions and Security
Documentation
Availability & Testing
What does success look like, and how can we measure that?
It would be successful if less mistakes and confusion happen for our users when web-ide acts the same on all branches.