So frustrating. You can only experience so many of these outages before you seriously have to start questioning whether it makes sense to continue to use GitHub (and many have already long since reached this point)
dgritsko
We self-host actions and this still impacted us. Incident resolved 30 minutes ago, but all our builds are still queued/pending. Maybe GitHub needs to replay some webhooks?
godzillafarts
When I type git in chrome, it autocompletes as githubstatus.com.
There has been degradation in their copilot cloud agent in the last few weeks (sessions erroring/disappearing, connections not working, etc) that is not on a status dashboard.
plasma
Dead in the water for actions that are merge requirements here.
tosser811
Even after they “resolved” it. I had two stuck actions in the queued state. Canceling failed. They are still stuck as “Queued” 2 hours later.
throw03172019
For those using GitHub Actions who want to be out of the blast radius of these outages, we at Depot built our own CI engine that speaks a GitHub Actions syntax but is our own control plane and runner [0]. Connected to all of the other things we do to accelerate CI, builds, tests, etc.
Happy to answer any questions or hook anyone up with an extended trial that wants to move things over to it.
comments (10)
dgritsko
godzillafarts
time0ut
OptionOfT
plasma
tosser811
throw03172019
Happy to answer any questions or hook anyone up with an extended trial that wants to move things over to it.
[0]: https://depot.dev/docs/ci/quickstart
kylegalbraith
Riemer
unconscionable