security: pin reusable PR autofix scheduler source - #706
Conversation
|
Warning Review limit reached
Next review available in: 8 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the 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 configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
Comment |
|
Superseded by #704. The hourly scheduler PR now includes this immutable called-workflow source binding, removes |
Pull request was closed
Security gap
The reusable PR review-fix scheduler was referenced by caller repositories at an immutable workflow SHA, but its checkout step loaded scheduler code from
main. GitHub documents that the ordinarygithubcontext in a reusable workflow belongs to the caller; the called-workflow source is exposed through the job workflow context.Change
canonical_refinputjob.workflow_repositoryat immutablejob.workflow_shaVerification required