Run on GitHub events
Trigger Engineering work from selected repository events and branches.
Choose the GitHub trigger category when work should respond to a source-control event. The routine uses its selected repositories, event types, branch filters, prompt, and session configuration.
Read the visual explanation
A GitHub event is compared with the routine’s selected events and branch filters. A matching event starts a run; an unrelated branch is skipped.
Configure the trigger
- Confirm GitHub access for the repositories.
- Select GitHub in the routine editor.
- Choose one or more events offered by the editor.
- Add branch filters when the routine should only match specific branches.
- Save, review the configuration, and test the prompt.
Supported events include PR creation, commit updates, edits, reopen, close, merge, readiness and draft changes, review requests, label changes, reviews, review comments, review-thread resolution, branch pushes, branch deletion, and merge-queue check requests.
Use the editor's labels to select the exact event. PR branch filters apply to the base branch; push and branch-deletion filters apply to the affected branch. An unrelated event or branch should not create the intended run.
Report a GitHub check
The GitHub-check option is offered for routines that include pull-request events. Enable it when the run should report its result as a check on the PR. It is not a general check switch for schedule-only work or every kind of GitHub event.
If a session runs but its check fails to publish, inspect the run's check error and GitHub installation access separately from the agent's execution result.
Write an event-aware prompt
Explain what should be reviewed and what the agent may change. For example, a PR review routine can ask for findings and evidence without granting permission to rewrite the branch.
Follow the event and session links in run history. A Test run verifies the routine execution path; it does not by itself prove that a real GitHub event is subscribed and matched.