We always kind of hated the term "pull request". It's pretty confusing for a beginner, and for a number of years led to the idea that GitHub didn't have code review at all in the product. (For that reason, I always thought we should just call them "Code Reviews", or just "Reviews".) There were a number of attempts to change it, but they all died.
It wasn't until last year when I got a beer with an ex-Atlassian employee when we chatted about this and realized we both had hated the term and had a number of attempts to change the nomenclature, but they fizzled out. Funny how things work out.
It may seem superficial, but if there's some way that you could give users the option to surface the pull request terminology rather than merge request, even if it's just a configuration option, you may find people more receptive to your product.
That being said, you can't POSSIBLY be serious that this one piece of nomenclature drove the decision between GitLab Enterprise and GitHub Enterprise. The latter costs roughly 5 times more than the former! Either this is unbridled hyperbole... or else money is no object at your company, and it's weird that you were evaluating GitLab in the first place.
And developers cost several orders of magnitude more than the software license.
The decision wasn't a matter of looking at features and making a logical decision. The decision was made by taking a sampling of developers and allowing them to test both systems and relying on their preference. They were unanimous that they preferred GHE. In drilling into their preference, the merge request nomenclature was the only issue that everyone mentioned they disliked.
And yes, the company wastes money like no other...it's part of the culture here and the result of having cash cow products that have very little competition. The only reason there was an evaluation was because one group inside the company was using Gitlab and another GH.com and the company decided to standardize on a single in-house solution.
Blasphemy. Atlanta can have their "Coke". Us North Carolinians drink Pepsi (born 1893 in New Bern, NC).
And to your point:
>The latter costs roughly 5 times more than the former! Either this is unbridled hyperbole... or else money is no object at your company, and it's weird that you were evaluating GitLab in the first place.
Never underestimate the ability of enterprises to over pay for a product despite the existence of cheaper, and arguably better solutions.
BTW, sytse, what's the best address to contact you about gitlab? There's something I'd like your thoughts on.
I found fetch/rebase/merge to be more difficult to wrap my head around (and I still can't do an interactive rebase/squash)
End result: people are confused and using a procedure that's more complex than what most of their contributions call for, but that goes away when you remember what the numbers for the company are.