Why would it need to encapsulate that Git is a pull/push model ? What the name should do is describe what it is, and it is a call for reviews before merging, so “review request” or “merge request” are names that would make sense. When web interfaces weren’t used, it made sense to ask for reviewers to pull for reviewing, but now it’s a minority of them that are pulled by reviewers.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !programmerhumor@lemmy.ml
Post funny things about programming here! (Or just rant about your favourite programming language.)
Rules:
Posts must be relevant to programming, programmers, or computer science.
No NSFW content.
Jokes must be in good taste. No hate speech, bigotry, etc.
Where is it MR and not PR?
gitlab / bitbucket
I wish MR would become the standard, I almost never pull an MR, PR doesn’t make sense anymore.
It’s the nature of pull vs push model. Merge Request doesn’t encapsulate that. But you do merge a pull request.
Why would it need to encapsulate that Git is a pull/push model ? What the name should do is describe what it is, and it is a call for reviews before merging, so “review request” or “merge request” are names that would make sense. When web interfaces weren’t used, it made sense to ask for reviewers to pull for reviewing, but now it’s a minority of them that are pulled by reviewers.