News for hackers. Stuff that matters.

A comment on Incident with Pull Requests, Git Operations and Issues. Parent comment

Re:Incident with Pull Requests, Git Operations and Issues by crote on Wednesday November 04, 2026 @12:36PM (#50368874)
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"?

[ Parent | on HN ]
Re:Incident with Pull Requests, Git Operations and Issues by chrisweekly on Wednesday November 04, 2026 @01:53PM (#50369926)
good bit of lore.

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

[ Parent | on HN ]
Re:Incident with Pull Requests, Git Operations and Issues by ajasmin on Wednesday November 04, 2026 @05:56PM (#50372623)
You can still do this with GituHub pull the PR branch locally, read the code, try thing out, rebase on main…
[ Parent | on HN ]