Re:Incident with Github.com
by parthdesai on Monday August 17, 2026 @10:50AM
(#49332002)
That's understandable, but surely there's a way to bypass it? You need to have a breakglass procedures lol
[ Parent
| on HN ]
Re:Incident with Github.com
by penultimatename on Monday August 17, 2026 @11:12AM
(#49332375)
“lol just use a workaround” doesn’t work in an environment with hundreds or thousands of employees coupled with audit, security, and other legal requirements to ship software.
Re:Incident with Github.com
by parthdesai on Monday August 17, 2026 @11:42AM
(#49332839)
If you're actually bleeding money, you better believe you'll get permissions for a workaround, if you know what you're doing.
It all ties back to the OP, where the issue you've might not be as bad as you think. I have been in situations where we have dropped all procedures to push a hot fix because we were actively bleeding money, and in situations where you know there is an issue, and you let it be.
Re:Incident with Github.com
by penultimatename on Monday August 17, 2026 @01:13PM
(#49334381)
What an odd hill to die on. Maybe I just lost a $30M client because they wanted an issue fixed now. Maybe my company would get sued for violating their contractual obligations if someone went cowboy to bypass procedures.
Maybe I pay for a service and I want that service to work consistently during core business hours.
"Just recreate GitHub internally."
Re:Incident with Github.com
by red-iron-pine on Monday August 17, 2026 @04:07PM
(#49336835)
"just redo the whole CI/CD pipeline bro, it's easy"