Dog food
I’m sure that they have replied, but the GitHub action to send it is stuck in a queue, somewhere
Code automation stalwarts have endured a frustrating start to the week after GitHub Action began tottering this morning, taking a number of carefully crafted workflows down with it. User problems were first reported at 9.44 UTC on 1 March, and a minute before the hour the Microsoft division admitted there was "degraded …
... for any "action" wouldn't you create these by hand with independence? Don't you want to?
I don't think people are really sitting around using all these actions every time they develop something. Probably more so in stages or once things are "finished", which at which point you'd want to write these yourself without co-dependency with "cloud" anything for peace of mind and for understanding exactly what they do and how to alter them. Ever wrote one of those "super" scripts that does so much that you have to babysit it when you just want to use a part of it?
FWIW from a non-GitHub user, these "Actions" seem more like traps.
You can't take your github actions spec and run them on GitlabCI, Travis, Jenkins, or CircleCI.
However, the logic of GH Actions is basically "take this docker image and run these commands inside it". That logic translates to any other CI software, so moving from one to the other is just a case of instrumenting the new CI software to do the same thing.