Repository navigation
ci: pass AI_REVIEW_APPROVAL_CEILING to ai-pr-review - #44
Conversation
Read the approval ceiling from the org variable AI_REVIEW_APPROVAL_CEILING. The fallback is request-changes, so the bot never posts APPROVE. This closes the SOC2 gap where a bot approval let a PR merge without a human review. Co-Authored-By: Claude <noreply@anthropic.com>
SummaryPasses a new Type: config Walkthrough (1 file)
AI Review Summary — generated by ai-pr-review |
There was a problem hiding this comment.
AI Review Findings
✅ Overall Risk: None | Findings: 0 (0 inline)
Review cost: $0.0336 · 12,292 tokens · 2 agents · Sonnet 5.5 · full breakdown
Not reviewed: No run of
silent-failure-hunter(the trigger for this agent did not fire).
Reply with a slash command to dismiss a finding. See the command reference.
AI Review — generated by ai-pr-review
jeffsheltren
left a comment
There was a problem hiding this comment.
LGTM — passes approval-ceiling (default 'request-changes') to both the container-action and slash-commands entry points.
Summary
Pass the org variable
AI_REVIEW_APPROVAL_CEILINGto ai-pr-review as theapproval-ceilinginput. The fallback isrequest-changes.APPROVE. A human must approve every merge.COMMENT. A Critical or High finding still postsREQUEST_CHANGES./ai-pr-review dismissfrom approving.Effect on merge
The new default applies when this PR merges, with or without the org variable. Set
AI_REVIEW_APPROVAL_CEILINGat the org level to change the value for all repos. Allowed values:approve,request-changes,comment.If a branch protection rule or an auto-merge rule waits for a bot approval, change it. Use
fail-on-findings: trueand a required status check instead. See the approval ceiling docs.Test plan
COMMENTorREQUEST_CHANGES, neverAPPROVED.