174 executed openhands agents to address unresolved comments on user's PRs. We've made changes in openhands_resolver/send_pull_request.py to update the user's PRs with the new generated code. Summary of changes made to the codebase are described below -
Checkout to "PR" branch instead of base commit ID when initializing repo
Commit to the existing branch, instead of creating a new one (this updates the existing PR with new code)
Add a comment on the PR indicating new updates were made
Reply to every unresolved comment thread with a summary of changes made by openhands
Updated test cases to reflect new workflow
Possible Future work
PR Update Message
Currently the message is fixed ("New openhands update"); this can be changes to be an AI generated summary of all updates made to each unresolved comment
Agentic Workflow
Inline review comments inherently localize to a specific code file. Openhands' agents don't utilize this context and spend time localizing to which file the comments apply to. Perhaps the user can have an indicator that forces openhands to start making changes from a specific file?
Possible benefits -
reliability
lowered cost
faster resolution time (especially when comments have smaller scopes)
Summary
174 executed openhands agents to address unresolved comments on user's PRs. We've made changes in
openhands_resolver/send_pull_request.pyto update the user's PRs with the new generated code. Summary of changes made to the codebase are described below -Possible Future work
PR Update Message
Currently the message is fixed ("New openhands update"); this can be changes to be an AI generated summary of all updates made to each unresolved comment
Agentic Workflow
Inline review comments inherently localize to a specific code file. Openhands' agents don't utilize this context and spend time localizing to which file the comments apply to. Perhaps the user can have an indicator that forces openhands to start making changes from a specific file?
Possible benefits -