Attempt to automatically select the ideal target branch when creating a merge request
Description
For my project in GitLab, we maintain a list of release branches, each one is a protected branch that follows a format like this:
v2.8 v2.9 v2.10 v2.11
Occassionally we backport a bugfix to a previous branch, but GitLab's default behavior is to create the merge request against master
(if we select the quick create option from a recently pushed branch).
Proposal
It would be nice if the default behavior (or configurable behavior) would look for the nearest common ancestor and use that branch, e.g. if a branch has 3 commits, and the 4th commit is the tip of v2.8, use that as the target branch.