Decide how each event is handled with event rules
Organizations write their own rules to skip, reroute or add instructions to pull request and pipeline events, and every event shows which rule decided it.
What happens to an incoming pull request or failed pipeline used to be decided by FerrFleet's code: the agent bound to the repository reviewed it, once per head commit. That default stays, and each organization can now put its own rules in front of it from the new Event rules page.
A rule matches on the kind of event, who opened the pull request and who triggered this particular event (kept apart, so "opened by Renovate, rebased by a person" is not mistaken for a bot update), the repository, the branches, the labels, the changed files and, for Renovate and Dependabot pull requests, whether the update is a patch, minor or major one. It can skip the event with a reason, send it to another agent, add instructions to that run's prompt, or run on every event instead of once per head commit.
Rules are read top to bottom and the first match wins. Below them, a Recent events list shows every event with the rule that decided it and what happened, so "why was this pull request not reviewed" has an answer without digging through logs. Every change to a rule lands in the audit log.