Run PR review only for same-repo PRs#82
Conversation
| github_token: ${{ secrets.GITHUB_TOKEN }} | ||
| pr_number: ${{ github.event.pull_request.number }} | ||
| review_prompt: ${{ inputs.review_prompt || 'connector' }} | ||
| review_prompt: ${{ github.repository == 'ConductorOne/github-workflows' && 'general' || inputs.review_prompt || 'connector' }} |
There was a problem hiding this comment.
🟡 Suggestion: With the if: github.repository != 'ConductorOne/github-workflows' guard removed from both workflows, pr-review.yaml and general-pr-review.yaml will both fire on pull_request events for ConductorOne/github-workflows. Both resolve to the general profile with the same ### General PR Review: summary heading, producing duplicate reviews with separate summary comments. Consider re-adding the guard here or on general-pr-review.yaml so only one runs on this repo.
General PR Review: Run PR review only for same-repo PRsBlocking Issues: 0 | Suggestions: 0 | Threads Resolved: 0 Review SummaryThis PR switches both review workflows from Security IssuesNone found. Correctness IssuesNone found. SuggestionsNone. |
| github_token: ${{ secrets.GITHUB_TOKEN }} | ||
| pr_number: ${{ github.event.pull_request.number }} | ||
| review_prompt: ${{ inputs.review_prompt || 'connector' }} | ||
| review_prompt: ${{ github.repository == 'ConductorOne/github-workflows' && 'general' || inputs.review_prompt || 'connector' }} |
There was a problem hiding this comment.
🟡 Suggestion: With the if: github.repository != 'ConductorOne/github-workflows' guard removed from both workflows, PRs to the github-workflows repo will now trigger both pr-review.yaml and general-pr-review.yaml. Both resolve to review_prompt: general and produce ### General PR Review: summaries, so they'll race to create/update the same comment. Consider gating one of the two workflows to skip on this repo, or giving them distinct summary headings.
General PR Review: Run PR review only for same-repo PRsBlocking Issues: 0 | Suggestions: 1 | Threads Resolved: 0 Review SummaryThis PR switches both review workflows from Security IssuesNone found. Correctness IssuesNone found. Suggestions
Prompt for AI agents |
Why
The PR review workflow needs to restore high-quality source inspection without running secret-backed Claude review on public fork PRs. Same-repo PRs are the intended automatic review scope; fork PRs should skip clearly instead of entering a privileged review path.
What this changes
Validation