Code review

Set review defaults

Workspace admins can change defaults under Settings, then Reviews. Start with a manual review if you want to check the setup before enabling automatic reviews.

Automatic reviews

Turn on Review new pull requests to review pull requests when they open. Use Skip draft PR reviews to exclude drafts. Re-review on every push controls whether new commits get another review on a pull request Arcanist already reviewed.

Add Skip rules to exclude a bot author, a repository, or a source branch pattern. Branch patterns support * and ? wildcards. Skip rules affect automatic reviews only, so you can still request a manual review.

After changing a rule, check a matching pull request to confirm the behavior you want.

Approval settings

Under Approve, select the blast radius levels at which a clear review can approve a pull request on GitHub. The choices are Low, Medium, and High. Leave all levels unchecked to post every review as a comment.

Review access

A person who requests a manual review must be an active workspace member with write, maintain, or admin access to the repository.

A review can use stored credentials only while the requester remains a workspace member with write access. Pull requests from forks do not receive your credentials when the application starts. A fork is a copy of your repository under a different owner.