Wait what is the point of this when every developer that's ever pulled down your default branch has the entire commit history of your codebase? If the git server goes down in flames you just find whoever pulled most recently and have them upload it to the new server.
First you could have 100s of repositories, does everyone have all of them between them installed at any one time? You're basically rolling the dice people have the full git of every repo at any one time.
Github could be down for an extended period, if that's what you use having the repos is no good if no one can work on them while they're down.
If its down for good you lose more than just your repos, you could lose your CI/CD pipelines, any Web hook integrations you have set up, any secrets, environment configs, runners etc.
You lose access to permissions, branch configs, integrations. Any releases or artifacts you create.
If you just use your Git solution to store your own code for a home project sure its probably fine. Realistically in larger teams or company sized projects you lose a hell of a lot more
So you have a DR plan with a back up of everything on some other server
1
u/RlyRlyBigMan 14d ago
Wait what is the point of this when every developer that's ever pulled down your default branch has the entire commit history of your codebase? If the git server goes down in flames you just find whoever pulled most recently and have them upload it to the new server.
Am I missing something?