Earlier quoted context omitted.
Looks like you know more about it than me, but it seems to me that the main challenge is being able to include the appropriate context, and train it to output a diff which you can then apply to the codebase. Definitely looking forward to the day I review my first AI-generated PR (beyond dependency updates of course).
Yup, those seem to be the key challenges. I've been making good progress on them, but there's plenty more work to do! On the topic of "AI-generated PRs", I used my tool to file a PR to the `glow` CLI tool. I don't know the go language, so I had my tool `aider` add the feature I needed. I mostly use glow to preview README.md for GitHub, so I wanted it to render line breaks like GitHub does. https://github.com/charmbra…
I've been iterating on a similar project, Talk-to-Repo.
It uses retrieval-augmented-generation to access the relevant parts of the code, and lets you chat and collect which code pieces you want.
Got stuck at generating good diffs, I'll be sure to look at how you've done it!
btw i started my project by turning another project, "Twitter explainer", on itself. It loaded its own code, i asked it to add new features and copy-pasted the results (with some tweaking and occasional trips to phind.com )... :)
https://github.com/Arjeo-Inc/talk-to-repo original project by Mark Tennenholtz: https://twitter.com/marktenenholtz/status/165156810719298355...