18 points | by evalsocket 3 days ago ago
5 comments
What does "fast" mean? Would have preferred to see benchmarks if this claim is to be made. I'm curious to see if it's faster than other CI workflow engines
Yeah sure but this tool is not exist to replace other CI workflow engines
“No YAML hell”
Later: “Example: YAML Workflow…”
Ok then
Apprently this claim got removed in README in c4710d3e17b3888946e2283a26ad54968f8e9196
So yes apparently they have joined the dark side and embraced the yaml hell
It's true—we removed YAML examples from the docs. While we do support YAML, we discourage users from writing it manually.
Right now, we're testing YAML support specifically for Go users in an early phase.
This tool is designed for end-to-end testing of Go applications, not as a CI workflow engine.
Since the CLI exists in multiple languages, YAML support remains for compatibility, but it's not the primary interface we want users to rely on.
What does "fast" mean? Would have preferred to see benchmarks if this claim is to be made. I'm curious to see if it's faster than other CI workflow engines
Yeah sure but this tool is not exist to replace other CI workflow engines
“No YAML hell”
Later: “Example: YAML Workflow…”
Ok then
Apprently this claim got removed in README in c4710d3e17b3888946e2283a26ad54968f8e9196
So yes apparently they have joined the dark side and embraced the yaml hell
It's true—we removed YAML examples from the docs. While we do support YAML, we discourage users from writing it manually.
Right now, we're testing YAML support specifically for Go users in an early phase.
This tool is designed for end-to-end testing of Go applications, not as a CI workflow engine.
Since the CLI exists in multiple languages, YAML support remains for compatibility, but it's not the primary interface we want users to rely on.