Warning: Some posts on this platform may contain adult material intended for mature audiences only. Viewer discretion is advised. By clicking ‘Continue’, you confirm that you are 18 years or older and consent to viewing explicit content.
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.
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.yamlto 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.