Automated Pull Request development with #AI agents for #craftcms, rough idea:
- #n8n for workflow handling (ticket/markdown --> start agent --> PR creation)
- server with #ddev and #claudecode (?) running, connect via SSH
- setup one ddev project automatically per PR / task
- serve preview via `ddev share` (maybe), to have preview URLs
Blocker: I'm not a #devops person at all, would assume that a MacMini would be most easiest as development server 🤓 But VM would be more profesh.
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)
…So I’m in a sitch where I’m trying to get an instance of #CraftCMS running.
- I understand that Craft uses Composer as its package manager, but to be honest my understanding doesn’t go much further.
- I don’t understand *when* it needs to run and when it doesn’t or why.
- I have a hosting context which *for reasons* are on a lower version of PHP than the version Craft needs
- There is apparently a way to tell Composer to use the version Craft needs…