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]

Taste Rating: 🔴 Needs improvement - Breaking change without verification

[CRITICAL ISSUES]

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

   • Evidence that the automation exists and is configured for this repository
   • Test results showing the automation triggers correctly on the expected events
   • A link to the automation configuration or dashboard

2. Documentation Not Updated: The plugins/pr-review/README.md still instructs users to download the workflow files being deleted (lines 11-12, 56-57). This will cause 404 errors after merge. This file should be updated in the same PR to reflect the new OpenHands Cloud automation approach.

[IMPROVEMENT OPPORTUNITIES]

3. Migration Plan: Consider keeping the workflows active until the automation has been verified in production. A safer approach:
   • Run both systems in parallel for a week
   • Monitor that the automation handles all cases the workflow previously covered
   • Then remove the workflows

[RISK ASSESSMENT]

⚠️ Risk Level: 🔴 HIGH

This PR removes critical infrastructure (automated PR reviews) without verifiable evidence that the replacement system is operational. If the OpenHands Cloud automation is not configured or fails, this repository and any downstream repositories using these workflow templates will lose automated code review capabilities.

Key Risk Factors:

• Removes established, working automation
• No verification that replacement is functional
• Documentation still references deleted files
• Other repositories may depend on these workflow templates
• No rollback plan documented

Recommendation: Do not merge until:

1. Evidence is provided that OpenHands Cloud automation is configured and tested
2. Documentation is updated to reflect the new approach
3. A verification period with both systems running in parallel has completed, OR
4. A maintainer with access to the automation dashboard explicitly confirms it's working

VERDICT:
❌ Needs rework: Provide evidence of working automation and update documentation before merging

KEY INSIGHT:
Removing working infrastructure without verified replacement is high-risk. Even if the automation is configured, proving it works should precede deletion.

---

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/extensions/actions/runs/26521656150

[all-hands-bot]

Taste Rating: 🔴 Needs improvement - Breaking change without verification

[CRITICAL ISSUES]

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

   • Evidence that the automation exists and is configured for this repository
   • Test results showing the automation triggers correctly on the expected events
   • A link to the automation configuration or dashboard

2. Documentation Not Updated: The plugins/pr-review/README.md still instructs users to download the workflow files being deleted (lines 11-12, 56-57). This will cause 404 errors after merge. This file should be updated in the same PR to reflect the new OpenHands Cloud automation approach.

[IMPROVEMENT OPPORTUNITIES]

3. Migration Plan: Consider keeping the workflows active until the automation has been verified in production. A safer approach:
   • Run both systems in parallel for a week
   • Monitor that the automation handles all cases the workflow previously covered
   • Then remove the workflows

[RISK ASSESSMENT]

⚠️ Risk Level: 🔴 HIGH

This PR removes critical infrastructure (automated PR reviews) without verifiable evidence that the replacement system is operational. If the OpenHands Cloud automation is not configured or fails, this repository and any downstream repositories using these workflow templates will lose automated code review capabilities.

Key Risk Factors:

• Removes established, working automation
• No verification that replacement is functional
• Documentation still references deleted files
• Other repositories may depend on these workflow templates
• No rollback plan documented

Recommendation: Do not merge until:

1. Evidence is provided that OpenHands Cloud automation is configured and tested
2. Documentation is updated to reflect the new approach
3. A verification period with both systems running in parallel has completed, OR
4. A maintainer with access to the automation dashboard explicitly confirms it's working

VERDICT:
❌ Needs rework: Provide evidence of working automation and update documentation before merging

KEY INSIGHT:
Removing working infrastructure without verified replacement is high-risk. Even if the automation is configured, proving it works should precede deletion.

---

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/extensions/actions/runs/26521656150

[juanmichelini]

LGTM

dismiss