Improve naming for GitLab Flow Merge Requests
Release notes
Problem to solve
When creating a merge request to Protected Branches (following GitLab Flow - where commits only flow downstream), the title attribute of the MR is the name of the source branch which is not a helpful name.
Screenshot of experience
Intended users
User experience goal
GitLab ought to inspect the source and branch (and determine if they are protected or not) and provide a more helpful title for the given MR.
Proposal
When two branches are protected and an MR is created for them, we have a default title of the MR as: Promotion of <source_branch> to <target_branch>.
Further details
Permissions and Security
Documentation
Availability & Testing
Available Tier
What does success look like, and how can we measure that?
What is the type of buyer?
Is this a cross-stage feature?
Links / references
Edited by Tim Poffenbarger