Skip to content

Auto-assign on fork PRs via pull_request_target - #50

Merged
bharvey88 merged 4 commits into
betafrom
fix/autoassign-fork-prs
Jul 14, 2026
Merged

Auto-assign on fork PRs via pull_request_target#50
bharvey88 merged 4 commits into
betafrom
fix/autoassign-fork-prs

Conversation

@bharvey88

Copy link
Copy Markdown
Contributor

Standardize auto-assign so it runs on PRs opened from forks.

The auto-assign workflow triggers on pull_request (or skips forks via an if: guard), so fork-submitted PRs never get auto-assigned — fork pull_request runs only receive a read-only GITHUB_TOKEN. This switches to pull_request_target, drops the fork-skip guard, and pins the assignee to bharvey88.

pull_request_target runs in the base-repo context with a write token. Safe here because the workflow never checks out or executes PR code — it only assigns.

Targeting the default branch (main) because GitHub runs the auto-assign workflow from the default branch for issues / pull_request_target events; a fix only on beta would stay inert. Matches ApolloAutomation/MSR-2#84.

🤖 Generated with Claude Code

bharvey88 and others added 3 commits July 7, 2026 14:35
Move label-check out of ci.yml into its own workflow on
pull_request_target so it gets a write token on fork PRs; plain
pull_request tokens are read-only there and the Apply Single Label step
fails (see #43). Same fix the other product repos got in June. ci.yml
permissions trimmed to contents: read since the CI build needs nothing
more.

🤖 Generated with [Claude Code](https://claude.com/claude-code)
Fix label check on fork-submitted PRs
@coderabbitai

coderabbitai Bot commented Jul 14, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@bharvey88, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 19 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

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.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 57d24c92-4a53-4ddf-bb97-ef5810cd3ee4

📥 Commits

Reviewing files that changed from the base of the PR and between 0b39a6e and bcd11b0.

📒 Files selected for processing (2)
  • .github/workflows/autoassign.yml
  • .github/workflows/label-check.yml
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch fix/autoassign-fork-prs

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

Comment @coderabbitai help to get the list of available commands.

@bharvey88 bharvey88 mentioned this pull request Jul 14, 2026
@bharvey88
bharvey88 changed the base branch from main to beta July 14, 2026 20:25
@bharvey88
bharvey88 merged commit c2e4eed into beta Jul 14, 2026
7 checks passed
@bharvey88
bharvey88 deleted the fix/autoassign-fork-prs branch July 25, 2026 20:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants