Review policy
Configure review events, draft behavior, exclusions, strictness, and publication limits.
Review policy is an instance default with an optional repository override.
| Field | Meaning |
|---|---|
review_on_open | Review newly opened pull requests. |
review_on_push | Review new commits on an existing pull request. |
review_on_reopen | Review when a closed pull request is reopened. |
review_on_ready | Review when a draft becomes ready for review. |
review_drafts | Permit eligible events while the pull request is a draft. |
strictness | Agent posture: LOW, MEDIUM, or HIGH. |
max_changed_files | Admission limit from 1 to 5000. |
comment_limit | Maximum published review comments from 1 to 100. |
excluded_authors | GitHub logins whose pull requests are not reviewed. |
excluded_paths | Path patterns omitted from review context. |
Draft handling and trigger handling are both required. For example, enabling review_on_push does not review a draft push when review_drafts is false.
Strictness changes what the agent is asked to surface. It does not change artifact validation, path boundaries, GitHub permissions, or the comment limit.
Choose exclusions narrowly. Excluded files are unavailable to finding generation, and an excluded author prevents the workflow rather than merely suppressing publication.
On later pushes, Tasuku reconciles findings by stable fingerprint and can resolve outdated GitHub threads. The policy controls whether that later review happens; it does not erase stored history.
Automatic feedback handling
Automatically handle PR feedback is a separate repository-only Automation setting and is disabled by default. It lets Tasuku investigate and respond to untagged feedback from repository owners, members, and collaborators, plus root inline comments from external review bots. Bot commands, replies, top-level comments, submitted-review summaries, and Tasuku's own comments remain ignored.
Handling can produce an evidence-backed reply, a focused clarification, no response, or a proposed code-change plan. Investigation is read-only, and inferred feedback never authorizes implementation; an authorized human must approve the plan first.
Automatic approval
Automatic pull request approval is a separate, repository-only setting in the repository's Automation tab. It does not require a repository-specific review-policy override and is disabled by default.
When enabled, Tasuku approves only an open, non-draft pull request whose current head is the exact commit reviewed and which has no open findings after policy exclusions and reconciliation. Tasuku-authored pull requests are never approved. If a later current-head review has open findings, Tasuku publishes the findings and dismisses its earlier active approvals.
This approval covers Tasuku's code review only. It does not query or override CI status, required checks, branch protection, or merge eligibility, and Tasuku does not merge the pull request.
The GitHub App needs pull request write access, and repository rules must allow the app to dismiss reviews. Review findings do not fail the Tasuku check run; an inability to publish or dismiss a review is an operational failure.