> So many MRs
Off topic: what’s the history behind the naming of Pull Request (PR) vs. Merge Request (MR)? I understand why both can be considered “correct”, but I’m curious why, say, GitHub uses PR and Gitlab uses MR.
Off topic: what’s the history behind the naming of Pull Request (PR) vs. Merge Request (MR)? I understand why both can be considered “correct”, but I’m curious why, say, GitHub uses PR and Gitlab uses MR.
In other words, I see a pull request in an open source project to be just "I have something nice in my fork, do you think it'll be useful upstream?", which is acceptable to reject, whereas in a team setting it's "I have a feature that I think is ready to merge - give it a look and see if I missed something before we put it in".