News for hackers. Stuff that matters.
Re:GitHub Incident by munificent on Tuesday March 22, 2022 @12:29PM (#30768150)
The worst case is discovering the hard way that your backup system isn't working and you haven't been diligent about spending the time to periodically test restores.
Re:GitHub Incident by dspillett on Tuesday March 22, 2022 @01:49PM (#30769198)
That's why testing of backups should be at least partially automated. Though you will always find a point where the automation, and automated tests to make sure that is working, and so on, get to the point where making a human responsible for sanity checking is most resource effective.
Re:GitHub Incident by ghusto on Tuesday March 22, 2022 @02:15PM (#30769490)
Pushing to multiple origins is not a hard thing.
Re:GitHub Incident by munificent on Wednesday March 23, 2022 @02:49PM (#30781866)
The risk is less about losing commits, since those tend to live on every devs machines too. It's about losing all of the other data like the issue tracker, comments, etc.