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.
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.