scitor.yaml recipe · Pro plan
Route tickets to the right team by category or label
Scitor's routing: config auto-assigns a ticket to a GitHub user or team the moment it's triaged — no GitHub Actions workflow needed, it's native to the product.
What this does
Rules are evaluated top to bottom and the first match wins. A rule can match an AI-detected category, a GitHub label, or both at once — and each maps to one or more assignees (usernames or team slugs).
What it does not do
Category-based rules require AI triage (ai: true) — on Free, category labels don't exist. Label-based rules (like the priority:urgent one above) work regardless, since priority labels are applied by default. A rule with no category or label, or no assignees, is silently ignored rather than erroring.
The config
Add this to .github/scitor.yaml.
# .github/scitor.yaml
routing:
auto_assign: true
rules:
# Route billing issues to the finance team
- category: billing
assignees: [alice, finance-team]
# Route urgent tickets to on-call
- label: "priority:urgent"
assignees: [oncall-team]
# Match both category and label (both must match)
- category: bug-report
label: "priority:high"
assignees: [bob, engineering-team]Full reference: scitor.yaml — Routing configuration
Never manually route a ticket again
Takes under 5 minutes. Free tier available. No credit card required.