Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Resolver] Create a more informative failure comment #5137

Open
ryx2 opened this issue Nov 20, 2024 · 0 comments
Open

[Resolver] Create a more informative failure comment #5137

ryx2 opened this issue Nov 20, 2024 · 0 comments
Labels
enhancement New feature or request resolver Related to OpenHands Resolver

Comments

@ryx2
Copy link
Contributor

ryx2 commented Nov 20, 2024

What problem or use case are you trying to solve?

When the openhands GH actions resolver fails to make a good PR, it just says

An attempt was made to automatically fix this issue, but it was unsuccessful. A branch named 'openhands-fix-issue-182' has been created with the attempted changes. You can view the branch here. Manual intervention may be required.

Describe the UX of the solution you'd like

Can the resolver create a summary of what was attempted, and why it failed in the comment, instead of this standard message? Otherwise, it takes way more time to dig through the github actions run / branch diff to find the issue

Do you have thoughts on the technical implementation?

I notice that the debug log from the send_pull_request often has information about whether or not the code changes were successful, just using these as the comments would be good

Describe alternatives you've considered

Additional context

@ryx2 ryx2 added the enhancement New feature or request label Nov 20, 2024
@mamoodi mamoodi added the resolver Related to OpenHands Resolver label Nov 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request resolver Related to OpenHands Resolver
Projects
None yet
Development

No branches or pull requests

2 participants