points by crote 3 days ago | 0 comments
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
[–] chrisweekly 3 days ago
good bit of lore.
related tidbit: in git, "pull" is basically shorthand for "fetch + merge".
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.