Found a small issue with github integration. If you create a github issue referencing a line in a file, using a non-main branch and then @ openhands, the agent will try to resolve the issue in the main branch. This can lead to it getting horribly confused and go round in circles. Notwithstanding that creating issues in branches is not exactly good practice. To reproduce: 1. Create a new branch in a repo 2. Modify a file in the new branch to have some sort of error or other issue 3. Click the context menu for a line near the new code and select "Reference in new issue" 4. Go to the issue and tag with openhands 5. Observe the conversation will work in the main branch rather than the referenced branch

@modern-businessperson-92319 please create an issue for this

Please provide a command starting with '#'.

@modern-businessperson-92319 #create-issue

Issue created successfully! _Title_: [Bug]: Incorrect branch used when resolving GitHub issues _URL_: https://github.com/All-Hands-AI/OpenHands/issues/9345

I was taking a look at past threads. I noticed that the bug “[Bug]: Incorrect branch used when resolving GitHub issues” was raised as https://github.com/All-Hands-AI/OpenHands/issues/9345 then marked as stale the automatically closed 😕 I get it that on a vast project with tons of issues things need to get closed that are features/questions/suggestions but closing a firm bug report automatically (that an agent should be able to verify!) seems like a bot misconfiguration? Just speaking up as a fresh set of eyes in the room 👀

Thank you, Simon, and sorry about that. Yes, we could be more attentive to issues I think, on the other hand many bugs get fixed without referencing the issues. I reopened it, and transferred to the cloud, as it seems to be about the cloud resolver

I'm sorry Simon, my fault. We try to be responsive but I dropped the ball on this ticket. I am curious if you've run into this same bug on OpenHands Cloud? I will see if we can reproduce it and then prioritize again.

I was browsing for context, and this was the first ticket I looked at 👀, so I thought to point out that the automation was closing bugs. I have just started with OpenHands, and it has done an impressive job at creating GitHub issues, PRs, writing regression tests, and upgrading some old zero-knowledge crypto code. As I do a structured approach, I wouldn’t hit this particular issue. Based on my experiences, telling OpenHands to investigate this bug to confirm it may work. Maybe that’s an idea 💡 if you can connect OpenHands Cloud to a “bug reproduction repo” and grant contributor access to a few folks who are interested, then folks can maybe get OpenHands to try to reproduce reported bugs (if possible). I am willing to volenteer my time to try to reproducing this bug 😀