> the runner is closed source My team runs our GHA runners on our own infrastructure using Actions Runner Controller (ARC). > The fact that you have to push a

> the runner is closed source My team runs our GHA runners on our own infrastructure using Actions Runner Controller (ARC). > The fact that you have to push a commit to the repo to test a change, and then wait for a runner delays everything indefinitely, and makes iterating really painful. Sounds like a mistake. Steps in jobs can often be run locally, and you could make choices in your jobs to make that more or less true. While there are certainly some things that you can only realistically test by triggering a CI job, many things can be tested locally. > writing pipelines in YAML is just painful... I invested 3 days to write a small DSL that compiles to GHA Yes, that can definitely be the case. But the thing about YAML is that it can easily be made a target for DSLs, as you demonstrated. I'd rather GHA use something common like YAML than force another DSL on to the world. It is better for users to decide if/what abstractions to use in front of YAML.