Post #838910
2026-03-26 04:20 UTC
How would you tackle this:
1. Button "Hey AI, try a PR!" in a Ticket (with description / goals as markdown)
2. AI agent launches a new, isolated craftcms project instance on a remote machine
3. Imports a database, setup of project (composer install, etc.)
4. Tries to implement task in a new feature branch
5. AI agent can check frontend (via browser extension or other tooling)
6. AI agent submits branch to git (Bonus: preview URls for reviewers)
7. human colleagues check the branch out, test it locally, give feedback
8. Iterate (or merge)
#craftcms #ai #webdev #vibecoding
Replies (1)
-
@mandrasch@social.tchncs.de 2026-03-26 04:21
Things I already know: - #ddev has a setting called `ddev config global --omit-project-name-by-default` --> projects start with a unique project name, their own database, etc. (https://www.fldrupal.camp/session/use-git-worktree-ddev-run-multiple-versions-same-site) - craft with ddev (or docker compose) runs on GitHub codespaces, but there are limits, etc. - claude code has a git worktree setting, where each session is automatically in a new git worktree I would assume that using a MacMini/own VM could be cheaper than GitHub Codespaces (?)