When using the GitHub resolver on a PR, automatically pipe in failure info

[neubig]

What problem or use case are you trying to solve?

One common use case of the GitHub resolver is to update a PR, and it is also frequent that the pr will have CI actions failing or merge conflicts. If we indicate to the agent that CI actions are failing or there are merge conflicts, we could improve the possibility that it will fix these while making any other changes.

Describe the UX of the solution you'd like

When they get help is over starts working on a PR, we make calls to the GitHub API to check if there are any merge conflicts or CI actions failing. If there are we add information about these problems to the initial prompt.

In the prompt, particularly when we describe GitHub actions, we can tell the agent to examine the GitHub workflow files, reproduce the problem locally, and fix and test it locally.

Describe alternatives you've considered

Instead of deterministically calling the GitHub API, we could also just notify the agent of the problem and allow it to use the GitHub API to gather any additional information that it needs. However this would require agent steps and cost for something that could just be added directly to the initial prompt, so it might be better to just add them right away.

[openhands-agent]

OpenHands started fixing the issue! You can monitor the progress here.

[openhands-agent]

A potential fix has been generated and a draft PR #5449 has been created. Please review the changes.

[github-actions]

This issue is stale because it has been open for 30 days with no activity. Remove stale label or comment or this will be closed in 7 days.

[github-actions]

This issue was closed because it has been stalled for over 30 days with no activity.