Skip to main content
Peeps reviews pull requests on the repositories you turn on. You set this up one repository at a time, under Settings > Code review > Review settings.

Who can use it

You need the Owner role. You also need the Peeps GitHub App connected, with access to the repositories you want reviewed.
If you don’t see Code review in settings, it isn’t turned on for your organization yet. Get in touch to request access.

Choose a repository

Pick one from the Repository menu. The menu lists every repository the GitHub App can access, with the ones being reviewed first. Beside it, a count such as 2 of 14 running shows how many are being reviewed. To add a repository to the menu, change what the installation can access on GitHub.

Turn it on

1

Turn on the switch

Use the switch beside Code review is off. A Not saved yet badge appears.
2

Save

Click Save changes. The heading changes to Code review is on.
Turn it off the same way.

What the settings do

When to review

Peeps doesn’t review pull requests from forks or bots, or its own peeps/* branches.

How to review

Second review adds an independent second reviewer, then a merge pass that keeps what either found.

Findings

Set each group to Comment or Ignore.

Verdict

Each takes a level: Critical only, Major and above or Anything. Request changes and Approve when clean also have a switch.

Presets

A preset fills in every setting at once, except Ready to merge, which stays as you set it. You still need to save. If you change a setting so that no preset matches, the page shows Custom settings. Review quality scores the current settings out of 99, as Light, Solid, Strict or Thorough.

Static code analysis

The Static code analysis section, after Verdict, holds the Complexity check. Its Complexity findings row sets whether the review only lists the functions crossing a limit (Comment) or also requests changes for them (Request changes). It runs a separate check on each pull request, named Peeps / static analysis, which names the functions crossing a limit. It has its own switch, independent of code review’s, and presets don’t change it. Save changes saves it with the rest. See Complexity check. If you don’t see the section, it isn’t turned on for your organization yet. Get in touch to request access.

Save your changes

Save changes saves the switch and every setting for the repository on screen. Save before you pick another repository. Changing the Repository menu drops anything you haven’t saved.

What Peeps sends for review

Turning a repository on sends each pull request’s diff and the repository’s files at its head to Anthropic and to Amazon Bedrock for review. Files named like secrets, such as .env files and keys, and files renamed from them, are left out.

If reviews stop running

The heading reads Code review isn’t running when a repository is saved as on but reviews can’t run. Can’t check right now means GitHub didn’t answer. The switch still shows what you saved. Try again.
Questions about code review? Get in touch.