Hacker News Reader

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

View on HN

Why are all you github people pulling on your requests?

I am requesting to merge my changes into the main branch.

Or you are requesting me to pull your changes into my branch.

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"?

good bit of lore.

related tidbit: in git, "pull" is basically shorthand for "fetch + merge".

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.

I have the opposite

Reply on news.ycombinator.com