Comment by CydeWeys
6 years ago
Fortunately, git is a DVCS, so anyone who checks out a repo has a complete copy of it.
Now, granted, it'd be a huge pain to track down all the people who had copies of the 1,500 different repos, and try to find as up-to-date as possible of a version of each, but I doubt they got anywhere close to potentially losing all their source code.
Incidentally this shows why it's a good idea to sync your repo to GitHub, even if the canonical repo is elsewhere: in addition to the usual reasons of incentivizing some contributors by giving them "GitHub credit", and increasing visibility of your project's code, GitHub can serve as a backup!
Also, on a side-note, 1,500 separate repositories?! That sounds way overkill. I wonder if they'd benefit from having a monorepo.
> 1,500 separate repositories?! That sounds way overkill. I wonder if they'd benefit from having a monorepo.
No it doesn't. Github has at least 20 million public repositories. Would they benefit by combining them into a monorepo?
GP is talking about the KDE project, not the entirety of GitHub.
And yes, a monorepo is usually the best approach in most cases for a project or even an entire company.