points by stack_framer 4 days ago | 0 comments
We use GitLab where I work. The only problem is it calls pull requests "merge requests," and I don't think I'll ever get used to saying "MR" instead of "PR."
[–] jaapz 4 days ago
[–] dutchbart 4 days ago
Or you are requesting me to pull your changes into my branch.
[–] crote 3 days ago
Because in the good old days when git was still distributed, a merge often started with sending someone an email to obtain your newly-coded commits via `git pull`ing your "gpu-drivers-for-linus" branch from some URL pointing to your personal GitWeb install. In other words: it was a request to pull your code.
Similarly: Why are the Gitlab people so happy to merge? Where is my "Rebase Request", "Squash Request", or "Cherry-pick Request"?
[–] ajasmin 3 days ago
You can still do this on a GituHub PR. Pull the branch locally, read the code, try things out, rebase onto main…
Once all is good, push into remote HEAD and GithHub should auto-close.
Though, larger project tend to leave the final upstream merge to GitHub itself. Better access control and it’s easier to serialize merges through a single queue for very active projects.
[–] chrisweekly 3 days ago
good bit of lore.
related tidbit: in git, "pull" is basically shorthand for "fetch + merge".
[–] hhh 4 days ago
I have the opposite
I am requesting to merge my changes into the main branch.