I literally set up some GitHub actions today for the first time in my life, I was really pumped about getting into the CI/CD game with my latest open repository. A couple of hours ago everything was going great, running a workflow needed maybe 40 seconds max. Now, they are not running at all. That all happened while I was thinkering with the yaml workflow file, so the disruption of the service made me believe that it was me who broke something :P it's been a nice first experience with CI/CD though, never going back to building my self.
Check my GitHub repo (see my bio) to see it's true haha
I thought I have started too many workflows in a short time and got temporarily restricted!<p>By the way, just discovered a nice library to test GitHub Actions locally: <a href="https://github.com/nektos/act" rel="nofollow">https://github.com/nektos/act</a>
Let's hope they didn't push faulty DNS records :D<p>But seriously, what's going on with all the service disruptions? From slack to all of facebook to GitHub (who had 7 incidents in September). Maybe centralizing the whole internet into a few providers isn't a good idea after all?
This reminds me of 2? years ago, when similarly multiple services failed in a window of a couple of weeks. Or was this last summer? I can't recall.<p>Anyways, Twitter will be down next week. You've read it here first.
This is happening far too often with such a vital product of the GitHub stack.<p>Our whole business[1] relies on GitHub Actions functioning. It just sucks.<p>[1] <a href="https://buildjet.com/for-github-actions" rel="nofollow">https://buildjet.com/for-github-actions</a>
Is <a href="https://gist.github.com" rel="nofollow">https://gist.github.com</a> down for everyone or it's just me? Not able to access it since weeks now.