chore: remove PR review GitHub Actions workflow

[xingyaoww]

Summary

Removes the PR review GitHub Actions workflow(s) as code review is now handled via OpenHands Cloud automation.

Changes

• Deleted .github/workflows/pr-review-by-openhands.yml
• Deleted .github/workflows/pr-review-evaluation.yml

Why

PR review functionality has been migrated to OpenHands Cloud automation, which triggers on:

• ready_for_review (established contributors)
• review_requested (when all-hands-bot is requested as reviewer)
• labeled (with review-this label)

The GitHub Actions workflow is redundant and can be removed.

This PR was created by an AI agent (OpenHands) on behalf of the user.

[all-hands-bot]

🟡 Acceptable approach - Clean deletion of redundant workflows, but missing critical verification

[CRITICAL ISSUES]

1. Missing Evidence: No proof that OpenHands Cloud automation is configured and working. Before removing these workflows, provide:

   • Link to the Cloud automation configuration
   • Example of Cloud automation successfully reviewing a recent PR in this repository
   • Confirmation that all necessary triggers are set up

2. Behavioral Change - Trigger Gap: The old workflow auto-triggered on opened for non-draft PRs from established contributors. The PR description lists Cloud automation triggers as ready_for_review, review_requested, and labeled - but doesn't mention opened. This means newly opened PRs won't get automatic review anymore. Is this intentional? If so, call it out explicitly in the PR description.

3. Documentation Inconsistency: The file openhands/usage/use-cases/code-review.mdx still documents and recommends the GitHub Actions workflow approach with example YAML configs. If Cloud automation is now the preferred approach for the docs repo itself, this documentation should be updated to reflect that (or at least note that the docs repo uses Cloud automation).

[IMPROVEMENT OPPORTUNITIES]

• Evaluation Workflow: The pr-review-evaluation.yml workflow provided feedback on review quality. Is this functionality replaced in Cloud automation, or is it being intentionally removed? Worth documenting either way.

[RISK ASSESSMENT]

• [Overall PR] ⚠️ Risk Assessment: 🟡 MEDIUM (potentially 🔴 HIGH if Cloud automation isn't ready)

This PR removes critical automation infrastructure. Risk is MEDIUM if Cloud automation is fully configured and tested, but HIGH if:

• Cloud automation isn't actually set up for this repository
• The trigger gap causes newly opened PRs to be missed
• There's an unexpected gap in review coverage during the transition

Recommendation: Do not merge until Cloud automation is verified working in this repository. Test by opening a test PR and confirming Cloud automation reviews it.

VERDICT:

❌ Needs verification: Deletion is clean, but requires evidence that the replacement is working and clarification on the behavioral change.

KEY INSIGHT:

Removing automation before confirming the replacement works risks breaking PR review coverage. The missing opened trigger represents a significant behavioral change that should be explicitly acknowledged.

---

Improve this review? If any feedback above seems incorrect or irrelevant to this repository, you can teach the reviewer to do better:

1. Add a .agents/skills/custom-codereview-guide.md file to your branch (or edit it if one already exists) with the /codereview trigger and the context the reviewer is missing (e.g., "Security concerns about X do not apply here because Y"). See the customization docs for the required frontmatter format.
2. Re-request a review - the reviewer reads guidelines from the PR branch, so your changes take effect immediately.
3. When your PR is merged, the guideline file goes through normal code review by repository maintainers.

Resolve with AI? Install the iterate skill in your agent and run /iterate to automatically drive this PR through CI, review, and QA until it's merge-ready.

Was this review helpful? React with 👍 or 👎 to give feedback.

---

Was this automated review useful? React with 👍 or 👎 to this review to help us measure review quality.
Workflow run: https://github.com/OpenHands/docs/actions/runs/26521635714

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated (UTC)
all-hands-ai	🟢 Ready	View Preview	May 27, 2026, 3:45 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.

[malhotra5]

LGTM

Cloud automation for pr review is ready