3 ms·
You can cause mayhem by force pushing all refs as empty though. Then you would likely need to get GH support on the line to restore a backup, if they had them f
by whalesalad 3y ago
You can cause mayhem by force pushing all refs as empty though. Then you would likely need to get GH support on the line to restore a backup, if they had them for you.
- dvngnt_ 3y agoI feel like at least one employ would have a clone of the repo no more than a few hours old.
- freedomben 3y agoIronically a lot of banks and big corps are moving to "cloud dev environments" so it's possible that Brody could have deleted all the dev containers too...
- whalesalad 3y agoyeah for sure that is definitely an urgent pagerduty request I might have sent once or twice before: /!\ DO NOT CLONE/PULL, DISCONNECT YOUR LAPTOP FROM WIFI
- sbergot 3y agoIt is really easy to protect you main branch. Github will actually warn you if don't have any protection policy on it.
- whalesalad 3y agoIt's also really easy to turn that off.
- telios 3y agoBut the commits will still be there even if the refs aren't, afaik? GitHub doesn't run gc that often.
- whalesalad 3y agoPossible? Try it and see =)