Somehow spooky for what github actions are used. On the one side it is cool to have hosted task runners with multiple options thanks to using vms in github actions, on the other side is the question: is this what github actions ate ment for?
> You can discover, create, and share actions to perform any job you'd like, including CI/CD, and combine actions in a completely customized workflow.
I guess it wasn't the goal initially, but it includes so much features now that it became a kind of _serverless_ orchestrator.
I don't use GitHub for that but my own self-hosted Gitea instance (so not quite serverless here), and I use it for this exact purpose: orchestrating containerized jobs without needing to setup something trickier. And since it's directly attached to a git repository, you don't need a second tool. So you know have everything configured and versionned at the same place.
Sure, it won't work if you need to run multiple big runners to do a job, but for small, periodic tasks like that, it's just so easy to do.