⑤ Configure your first event trigger

Goal

Configure an Event Trigger: when a new GitHub PR opens, automatically run the code-review agent.

Prerequisites

• Finished Tutorial ③ (manual review works)
• Admin on a GitHub repository

Steps

Step 1 — Draft trigger settings (~5 minutes)

Dashboard → Event Trigger → Create:

• Name: github-pr-auto-review
• Source: GitHub Webhook
• Filters:
  • repo = myorg/myrepo
  • event_type = pull_request
  • action ∈ [opened, synchronize]
• Session policy: reuse by repo/pr_number (same PR → same Session)

Step 2 — Bind skills + prompt (~10 minutes)

Prompt applied when the trigger fires:

PR event: {{payload.pull_request.html_url}}
Action: {{payload.action}}.
Call /code-review on this PR with MISRA-C:2012 and post findings to the PR thread.

Triggers deliver events; agents follow the prompt—extend with “review + run tests” by editing this text.

Step 3 — GitHub Webhook (~5 minutes)

Platform issues a webhook URL similar to:

https://combo-agent.example.com/webhooks/{tenant}/gh-pr-auto-review
Secret: <HMAC key>

GitHub repo → Settings → Webhooks → Add:

• Payload URL = above
• Content type = application/json
• Secret = above key
• Events = Pull requests

Step 4 — Test (~5 minutes)

Open a small PR. Verify:

1. GitHub shows delivered (200)
2. Dashboard → Trigger log shows receipt
3. Matching Session spins up; agent reviews
4. PR thread shows AI review

Step 5 — Tune (~5 minutes)

Adjust as needed:

• Debounce — collapse multiple pushes within one minute
• ConflictPolicy — if a session is busy: skip / queue / parallel
• Filters — ignore Draft PRs or specific paths

Acceptance checklist

• New PRs automatically invoke AI review
• Rapid pushes don’t spam reviews (debounce works)
• Review comments appear on the PR
• Trigger logs complete and inspectable

Next steps

• Event Trigger deep dive
• Cron schedules for time-based firing
• Webhook integration
• Webhook event catalog

FAQ

Q: Trigger failures—how to debug? A: Dashboard → Trigger log; failures land in a dead-letter queue.

Q: Compound conditions? A: Yes—Compound Trigger, e.g. “PR opened and CI green” before review runs.