fix: simplify PR_URL_OVERRIDE logic to resolve review enumeration bug

[don-petry]

Problem

PR #403 and potentially other PRs were not being reviewed despite the pr-review.yml workflow running successfully. Root cause analysis identified that PR_URL_OVERRIDE was evaluating to an empty string for pull_request synchronize events.

Root Cause

The PR_URL_OVERRIDE environment variable used a complex YAML boolean expression with nested && operators within || chains:

PR_URL_OVERRIDE: >-
  ${{
    inputs.pr_url
    || github.event.client_payload.pr_url
    || (github.event_name == 'pull_request_review' && github.event.pull_request.html_url)
    || (github.event_name == 'pull_request' && github.event.pull_request.html_url)
    || ''
  }}

This expression had operator precedence issues or evaluation logic that caused github.event.pull_request.html_url to be treated as falsy/null, resulting in PR_URL_OVERRIDE becoming an empty string. When empty, the enumerate step would fall back to list-prs.sh, potentially missing the PR or encountering transient issues.

Solution

Simplify the expression to directly access github.event.pull_request.html_url without event_name checks, matching the pattern already working successfully in the concurrency group:

PR_URL_OVERRIDE: >-
  ${{
    inputs.pr_url
    || github.event.client_payload.pr_url
    || github.event.pull_request.html_url
    || ''
  }}

This works because:

• pull_request events (ready_for_review, reopened, synchronize) have github.event.pull_request.html_url
• pull_request_review events (submitted, dismissed) have github.event.pull_request.html_url
• check_suite events are handled separately via CHECK_SUITE_PRS
• workflow_dispatch and repository_dispatch are handled via inputs

Testing

After this PR is merged, PR #403 or similar ready PRs should be properly reviewed on the next synchronize event. The enumerate step will now correctly populate PR_URL_OVERRIDE and use direct single-PR mode rather than falling back to list-prs.sh enumeration.

[gemini-code-assist]

Note

Gemini is unable to generate a review for this pull request due to the file types involved not being currently supported.

[coderabbitai]

Warning

Review limit reached

@don-petry, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 54 minutes and 47 seconds. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 3c16384b-63b3-44b0-a18e-e6a5571821f9

📥 Commits

Reviewing files that changed from the base of the PR and between 2c7fc09 and fe5dd64.

📒 Files selected for processing (1)

• .github/workflows/pr-review.yml

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/pr-review-url-override

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[Copilot]

Pull request overview

Simplifies PR_URL_OVERRIDE computation in the PR review workflow to reliably capture the PR URL across pull_request / pull_request_review events, preventing unintended fallback to batch enumeration.

Changes:

• Replaced event-name-gated PR URL selection with a direct github.event.pull_request.html_url fallback.
• Keeps the existing override priority order: workflow_dispatch input → repository_dispatch payload → PR event context → empty string.