Stop PR webhooks from automatically dispatching semantic reviews #44

Closed
opened 2026-05-02 19:41:24 -07:00 by jwilger · 0 comments
Owner

Problem

PR webhooks currently trigger reviews immediately. Once CI-triggered review dispatch exists, webhook-triggered reviews would bypass the workflow's needs: gating and spend LLM tokens before deterministic checks pass.

Direction

Keep PR webhooks for low-cost state handling and chat support, but make normal semantic review dispatch originate from the CI action path.

Acceptance

  • PR open/synchronize webhooks no longer dispatch a semantic review by default.
  • Webhooks still support chat-command/poller behavior and any low-cost bookkeeping required for persistent history/learnings.
  • @auto_review re-review or other explicit chat commands can still force a review through the gateway, with clear status/logging that it bypassed CI gating intentionally.
  • Gateway status messages make the waiting-for-CI/action-triggered lifecycle understandable to PR authors.
  • Docs explain that projects choose review prerequisites in workflow YAML.

Dependencies

Blocked by: #42 and #43.

## Problem PR webhooks currently trigger reviews immediately. Once CI-triggered review dispatch exists, webhook-triggered reviews would bypass the workflow's `needs:` gating and spend LLM tokens before deterministic checks pass. ## Direction Keep PR webhooks for low-cost state handling and chat support, but make normal semantic review dispatch originate from the CI action path. ## Acceptance - PR open/synchronize webhooks no longer dispatch a semantic review by default. - Webhooks still support chat-command/poller behavior and any low-cost bookkeeping required for persistent history/learnings. - `@auto_review re-review` or other explicit chat commands can still force a review through the gateway, with clear status/logging that it bypassed CI gating intentionally. - Gateway status messages make the waiting-for-CI/action-triggered lifecycle understandable to PR authors. - Docs explain that projects choose review prerequisites in workflow YAML. ## Dependencies Blocked by: #42 and #43.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Slipstream/auto_review#44
No description provided.