Replies: 3 comments 2 replies
-
This is an interesting idea, I would see this as an optional behavior and a nice to have rather than a need at this point. |
Beta Was this translation helpful? Give feedback.
-
I'll bump this. It's not just checking in the code generated, but using the code generated (previously, or that exists already in the repo) to build upon. That is, run GPT Engineer at different times, and it uses the existing codebase as a starting point. |
Beta Was this translation helpful? Give feedback.
-
I would pay for this. Anything devops related seems like moving a mountain just to take a step. Not to deviate on the topic here, but as it is related ( somewhat ), the thing on the top of my AI capability wish list is help with deployments/configuration/devops. |
Beta Was this translation helpful? Give feedback.
-
I propose GPT Engineer should check in his code on a specified github repo.
This could be the beginning of a CI CD strategy.
Beta Was this translation helpful? Give feedback.
All reactions