This is the realm of standard recovery planning though, isn't it? Like, your processes should be able to handle this, because it's routine: GitHub goes down at least once per month for long enough for them to declare an incident, per https://www.githubstatus.com/history . E.g. one should think carefully before depriving onself of the break-glass ability to do manually what those pipelines do automatically.

yes, we do have break glass procedures.

i guess my pedantic point is GH itself is central to many organizations, detached from git itself of course. I can only hope the same is NOT true for OpenAI but maybe there are novel workflows.

just to be clear i do not like github lol