I can already tell by their example that I don't like it. I've worked with a bunch of different container-based CI systems and I'm getting a little tired seeing the same approach by done slightly differently.

    steps:
      - name: backend
        image: golang
        commands:
          - go build
          - go test
      - name: frontend
        image: node
        commands:
          - npm install
          - npm run test
          - npm run build

But the moment things start to get a little complex then that's when the waste starts happening. Eventually you're going to want to _do_ something with the artifacts being built, right? So what does that look like?

Immediately that's when problems start showing up...

- You'll probably need a separate workflow that defines the same thing, but again, only this time combining them into a Docker image or a package.

    - I am only now realizing that woodpecker is a fork of Drone. This was a huuuge issue in Drone. We ended up using Starlark to generate our drone yaml because it lacked any kind of reusability and that was a big headche.

    - GitHub's free component honestly hurts itself here. I don't have to care about waste if it's mostly free anyways.

I really wish someone would take a step back and really think about the problems being solved here and where the current tooling fails us. I don't see much effort being put into the things that really suck about github actions (at least for me): legibility, waste, and the feedback loop.