I am able to open a new PR with the diff show in Codex but there is no option to update this PR after I request some more changes from Codex. This makes iteration difficult.
5 Likes
Same; it also prevents spinning up multiple agents operating on the same file / branch, because the second cannot pull changes that the first makes
1 Like
I am facing the same issue, its not able to get the latest changes and resolve conflicts! do we need to manually pull the latest changes on each branch?
1 Like
Being able to push further iterations to the existing branch already created for a PR would be ideal. The way I have been dealing with this is once I’ve created a PR, any subsequent iteration is done from entirely new tasks targeting the PR branch that was created. More cumbersome, but does kind of get you there.
Just wanted to chime in and say I’m also finding this limitation pretty frustrating. Not being able to update an existing PR means I have to create a new one for every little change, which really disrupts the development flow. It makes Codex feel less helpful than it could be, especially when trying to iterate quickly. Hoping this feature gets added soon!
Yep, this is a really big issue. Reusing the same feature branch on subsequent requests would fix the issue and then an option to push back to that branch. As it stands today, you lose the thread when submitting multiple requests.
It would be optimal if a single task of Codex would be associated with one (and only one) branch. And if we could have the conversation inside a GitHub Issues page, it would be even better, to keep the active PR as part of the context, which I am not sure we are doing right now.