|
|
|
|
|
by ryandrake
3 days ago
|
|
Yea, I keep saying: "Git doesn't need a hub." One of the greatest features of git is that it is not reliant on a centralized repo! Why graft centralization onto a tool that doesn't want it? The non-git features of GitHub, like actions and CI and the issue tracker and all that stuff are fine, but I'd argue don't really belong as part of your source control system. If you need that stuff, you should be able to pick and choose the tools you want to use, rather than just live with whatever GH gives you. But they really have nothing to do with git. |
|
But, even though the Linux the project created git specifically for their own workflow, and is in the running for the largest and most complicated decentralized software project ever known, they still operate git.kernel.org. They still have a central master repository server.
Just because git clone gets you a first class copy of the repository doesn't mean you don't need a source of truth or a centralized master to operate and coordinate the project. Control is not the totality of the benefits of centralization, and we should not confuse the structure of the tool with the best structure of a project that uses that tool.