top | item 44408948 (no title) zaps | 8 months ago “No YAML hell”Later: “Example: YAML Workflow…”Ok then discuss order hn newest flysand7|8 months ago Apprently this claim got removed in README in c4710d3e17b3888946e2283a26ad54968f8e9196So yes apparently they have joined the dark side and embraced the yaml hell evalsocket|8 months ago 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.
flysand7|8 months ago Apprently this claim got removed in README in c4710d3e17b3888946e2283a26ad54968f8e9196So yes apparently they have joined the dark side and embraced the yaml hell evalsocket|8 months ago 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.
evalsocket|8 months ago 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.
flysand7|8 months ago
So yes apparently they have joined the dark side and embraced the yaml hell
evalsocket|8 months ago
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.