3 ms·
They are instead focusing on Agentic Workflows which used natural language instead of YAML. https://github.com/githubnext/gh-aw https://github.com/githubnext/g
by captn3m0 1y ago
They are instead focusing on Agentic Workflows which used natural language instead of YAML.
https://github.com/githubnext/gh-aw https://github.com/githubnext/gh-aw
- woodruffw 1y agoI personally find this pretty concerning: GitHub Actions already has a complex and opaque security model, and adding LLMs into the mix seems like a perfect way to keep up the recent streak of major compromises driven by vulnerable workflows and actions. I would hope that this comes with major changes to GHA’s permissions system, but I’m not holding my breath for that.
- kstrauser 1y agoKnow what I love in a good build system? Nondeterminism! Who needs coffee when you can get your thrills from stochastic processes. Why settle for just non-repeatable builds when you can have non-repeatable build failures!
- joelfried 1y agoWould a smart AI accept such foolishness? I doubt it. It'll still use something deterministic under the hood - it'll just have a conversational abstraction layer for talking to the Product person writing up requirements. We used to have to be able to communicate with other humans to build something. It seems to me that's what they're trying to take out of the loop by doing the things that humans do: talk to other humans and give them what they're asking for. I too am not a fan of the dystopias we're ending up in.
- bluGill 1y agoWould it, or would it rewrite / refactor the logic every time. I'd expect the logic to remain as it for months, but then change suddenly without warning when the AI is upgraded.
- kstrauser 1y ago“Just make it generate YAML and cache that until the prompt changes!” Orrrrr… just keep that YAML as the sole configuration input in the first place. Use AI to write it if you wish, but then leave it alone.
- dehrmann 1y agoWhat I'm hearing is we need to invent LLM-based compilers.