> Copilot services took longer. Errors in those services triggered a client-side retry loop that increased traffic during recovery. Let's pretend that the scal

> Copilot services took longer. Errors in those services triggered a client-side retry loop that increased traffic during recovery. Let's pretend that the scale traffic is with the number of commit/pr and not self-inflicted with all the copilot eye candy features that were vibe-coded-added to GitHub. In addition they say that they will continue their migration to azure and that azure is supporting their actions run. But GitHub actions is one of the things that was the most constantly broken without multiple outages recently. So I have the feeling that it proves the point that part of the stability issues is also due to their forced usage of azure.