Re:Incident with Github.com
by ryandrake on Monday August 17, 2026 @10:20AM
(#49331448)
Git doesn't even need to be "hosted" anywhere. That's the point of it being distributed. What needs to be hosted somewhere are all the barnacles (like issue tracking, code reviewing, CI, and so on) that have grown out around git, that people and businesses have become dependent on.
[ Parent
| on HN ]
It doesn't have to be. But without a hosted "source of truth", it's kinda hard to actually distribute it, and have a way to accept pull/merge requests/patches.
LFS files sorta do need to be hosted. At least, it exists because full clones are untenable for many projects.
Which is why they cleverly moved the central story of a software change from the commit to the PR. Commits migrate automatically with the repo. But migrating PR descriptions and comments takes engineering effort.
Rhetorically, why can't folks add the feature of PRs to Git? Git is fundamentally just a graph manipulation engine and data structure. It would just be another object type, in a layer which sits above the normal commit graph. Obviously there is no "just make X" in software, but this feels reasonably achievable, and would have tremendous benefit for the cost.
Re:Incident with Github.com
by pwdisswordfishq on Monday August 17, 2026 @11:23AM
(#49332549)
Where would you put comments then? Sure, there’s always mailing lists, but even so, someone still has to host Mailman.
I do think GitHub has positively contributed to the software industry and open source. It’s been enshittified for sure, but it has had a golden era.
In regards to issue tracking there are alternatives. Epiq is a git-native (vendor agnostic) issue tracker you self-host: https://ljtn.github.io/epiq/