Repository navigation
Conversation
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
|
@OpenHands /codereview-roasted Review exactly commit 94aeb24. If the PR head changes, report that and do not approve another commit. Review only: do not push code, merge, deploy, or change attribution. Check correctness, regression coverage, and whether the PR validation claims match the evidence. Keep code comments short. Post the substantive review and link it in your completion message. End the substantive review with these plain lines (no code fence), choosing one verdict: REVIEWED_HEAD: 94aeb24 Use VERDICT: CHANGES_REQUESTED instead when findings require changes. If unable to review, explain the blocker without an approval verdict. |
|
Uh oh! There was an unexpected error starting the job :( |
Summary of changes
The Jira Cloud page told users to mention exactly one repository. With OpenHands/enterprise#1085, a Jira Cloud issue or comment can name several repositories and OpenHands starts one conversation with all of those it can access (up to ten), comment mentions first. This updates the "Start OpenHands from an issue" section to describe that and the reply, and replaces the "multiple repositories were found" troubleshooting entry with the "Could not access any of the mentioned repositories" one.
This should merge with or after the enterprise change ships.