Create Merge Request flow - default to master unhelpful
Created by: mhfen
Upon pushing new commits, the Dashboard displays a helpful "Create Merge Request" button. In previous versions, this would take the user to a new page with the update branch pre-loaded as the Source Branch. The Target Branch would not yet be loaded, since this updated branch could be a feature branch or a hotfix branch not going straight into master. This was extremely helpful and the flow made a lot of sense.
Now, in Gitlab 7.2.1, the flow has become cumbersome and unhelpful. The button takes the user to a page with the update branch preloaded in Source Branch and master branch preloaded in Target Branch. The way most programmers source control, master is merged to the least of all branches. There could be 50 feature branches merging to a project branch throughout the life of a project, for example. Then that would go to master after testing.
On top of that, if you want to edit the Target Branch, it takes you to an entirely new page with nothing loaded in Source or Target branches.
The quick "Create Merge Request" button was a previously very helpful flow. It's now a cumbersome flow that defaults to master when most git flows go to master least.