Merge is so much clearer (as a non-coder). I've always wondered why its called Pull Request - When as a contributor, you are pushing your code into someone else's codebase and merging it going forward.
Actually, that's not what's happening. What's happening is that the project maintainer is pulling in your changes, from your repository. It's a decentralized vs centralized thing.
I think you're missing the forest for the trees for here. It may technically be a pull, but the thought process involved is most typically "I want to send my code over to _____".
Unfortunately git is to powerful to handle its UX like that. Users have to understand the model behind it. If you have ever tried to work with teammates, who did not fully get yet how git works, you know what world of pain that is. They have to think like git works, you cannot abstract this away into their understanding of SCM.
No, this is actually a different meme. This is because all "forks" of a project on github are kept in the same backend repository, using namespaced branches. You can confirm this by making a commit on your repo, and then navigating to that commit hash on someone else's repo that's forked from the same project.
I think it's arguable either way, honestly. When you order a pizza, would you say it is a Pizza Request, a Toppings Request, a Transaction Request or a Request for Pizza with My Toppings Merged into the Default Configuration?
Pull Request makes sense to me, Merge Request makes sense to me too. To others, one may resonate more. Rosetta Stone posts like this can be helpful to people who are used to a particular vernacular, and I don't think the semantic distinction is itself the point. Other than the Gist comparison (which I mentioned in another comment), I think this post was helpful.
It's truly inspiring how _present_ Gitlab are in the communities they serve.
Yeah, you are right. "Pull request" in itself could be parsed as a command, but it is a thing really. Used in a command you would say "Send pull request". Where send is the verb and "pull request" is the object. In my native language it would actually be a single word. I have seen some people write it as pull-request, which removes the ambiguity.
Note that "Merge request" doesn't solve this problem.
From a user-interface design perspective I would say it would be bad to have a button or link that solely says "pull request" or "merge request". It should probably be preceded by a verb such as view, send or process.
Also, pulling a pull request or merging a merge request is just weird and doesn't make sense.
