OK, so, the project looks cool, and I’m grateful for any OSS. Let me put that up front.

However. I’m going to bitch a little about standards. Every single CI tool re-invents their own build syntax. It’s always some .XYZ.yaml file in your project; they all look almost exactly alike and have essentially the same structure and operations, but they each feel the need to make things slightly differently, making them non-portable between systems.

Compare Woodpecker’s .woodpecker.yaml to Github’s .github/workflow.yaml, to Sourcehut’s .build.yaml… they’re almost, but not quite, all the same.

Please, for the love of dog, pick a fucking standard so I don’t have to remember each and all of your special snowflake terminology for the same god-damned functions. There is no standard; not even in ForgeFed. So if you’re developing a new CI system, please please just pick one of the existing ones - I don’t care which, because they all do the same god-damned things - and use it. It’ll be one less syntax I’ll have to learn if I want to try your project.

Please. I’m literally begging you. Stop re-inventing this wheel: it’s going to look exactly like all the other wheels, only be incompatible.

Ah I hadn’t heard of Woodpecker. It’s a fork of Drone which apparently is now proprietary.

Still it could do a better job of explaining why I would use it over e.g. Gitlab, which it seems to be nearly identical to. Also relying on Docker images means you can’t target Windows or Mac anymore which is a pretty fundamental limitation for a huge number of projects.