Harden label-check for pull_request_target callers#24
Conversation
Pass the PR body via an environment variable instead of interpolating it into the run script, closing a script-injection vector. This makes the workflow safe to call from pull_request_target triggers, which device repos need so label-check works on fork PRs (fork pull_request runs only get a read-only token and cannot add labels). Drop the checkout step since no repository files are used.
|
Warning Review limit reached
More reviews will be available in 30 minutes and 55 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 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 configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
2 participants
Passes the PR body through an environment variable instead of interpolating it into the shell script, closing a script-injection vector, and drops the unused checkout step.
This prepares the reusable workflow to be called from \pull_request_target\ triggers in the device repos. Fork-submitted PRs (like ApolloAutomation/AIR-1#97) currently fail the Label Check because \pull_request\ runs from forks get a read-only token and cannot add labels (\403 Resource not accessible by integration). The device repos will switch their label-check callers to \pull_request_target\ in follow-up PRs; this PR should merge first since \pull_request_target\ runs with a write token and must not execute PR-controlled content.
🤖 Generated with Claude Code