So, right now, when I get Codex to do some kind of change, before I want to submit it to the world I need to merge the PR. Then I download it locally, kick the tyres, and release it. 90% of the time it’s fine. 10% of the time, changes are needed. In those 10% of times (more if I’m asking for a UI change), the flow is quite clunky. First of all, I now have a set of merged changes that are not actually ready for merging/release. I could use a branch, but that’s also somewhat more clunky than I’d like. Or I can wait until Codex provides another PR, though somehow that is also cumbersome because it clashes with its own previous PR and so I have to manually resolve merge conflicts with its own previous PR on Github. Not great.
All of this would be a lot easier if it were possible to just test the changes before merging. In my case, the project is a Rails app, so what I imagine in an ideal world is there are instructions for how to spin up a test system with fixtures loaded, and then it gets opened up on a VM on some random URL with a special port, I go there, check what it looks like, and if I don’t like it, ask Codex to make a few further changes before opening the PR.
Perhaps there’s another different, even better workflow - if so please let me know. But this is what I’m imagining would improve my ability to use Codex for everything right now.