But all the other delis are doing it as well. So is your supermarket. So is your farmer (somehow they figured out how to add salt to the veggies they sell at the farmer's market!)... Whaddya gonna do? Grow your own? THE SEEDS SHALL HAVE SALT TOO, has been decreed...
> Instead of writing bespoke scripts that operate over GitHub using the GitHub API, you describe the desired behavior in plain language. This is converted into an executable GitHub Actions workflow that runs on GitHub using an agentic "engine" such as Claude Code or Open AI Codex. It's a GitHub Action, but the "source code" is natural language in a markdown file.
This seems like a real headache to me. I understand the value proposition of LLMs in the development cycle, but CI/CD is probably the last place where I want any degree of nondeterminism.
This looks like backwards. I would understand using a LLM to generate a GitHub Actions YAML, but always running your action from a Markdown file seems extremely wasteful in terms of resources.
Edit: ok, looking at example it makes more sense. The idea is to run specific actions that are probably not well automated, like generating and keeping documentation up-to-date. I hope people don't use it to automate things like CI runs though.
Don’t worry. These immutable distros break in completely new and unexpected ways, especially since a lot of programs don’t quite gel with it or with the flatpak stuff (e.g. mdns still not really supported)
Sorry, RAM is too expensive these days to run two instances of Chrome on the same system. Maybe the time has come for some VC-backed startup to start a rent-seeking business for streaming your development environment from the cloud?
I know there were attempts for this before but they were just banking on the fact that the average dev env is an absurd collection of hacked together tools that is both fragile and nigh impossible to set up for new devs. Now they have a financial angle as well /s
reply