RE-OPEN 35054
Someone from the product team at gitlab needs to look at issue 35054 from a non-biased lens. It is completely non-intuitive UX which is causing a lot of people issues. Merging branches is the bread and butter of GIT, if you are changing a fundamental primitive (mergers) of how a technology is expected to work, by reversing the direction of the merge request (opposite to the direction provided explicitly by the user) without warning that is a major issue.
I am honestly surprised this issue has not been addressed in a meaningful way in over one year.
Edited by Shiv Sinha