Turn on review

Graphide review checks each pull request: an agent with the graph of your code finds what the change reaches and what it breaks. In beta, a live environment runs your old and your new code to show a breakage happening. Each review posts one comment on the pull request, updated with every push, and a Graphide review check. The whole review is on graphide.com.

It needs no Graphide CI.

What a review does

1. An agent with the graph. Beside the diff, the reviewing agent gets our graph of your code: callers, routes, tables, services and your rules, so it sees what the change reaches.
2. A live environment (beta). A test runs on your old code and your new code. Passes on the old, fails on the new: the finding is marked Verified, with the run attached. Ask us to turn it on for a repository. Where that code runs: Review security.
3. Live data flows (beta). Production-shaped and synthetic inputs through the old and the new build. Ask us to turn it on for a repository.
4. The visualizer. The same graph and evidence, drawn for whoever approves. The visualizer.

Turn it on

After you connect GitHub, your dashboard lists the repositories the GitHub App can read. Turn on the ones to review. Review starts on the next pull request.

Reviews come on pull requests. A project that lands its changes straight on its main branch gets none.

How a repository is reviewed

Each repository’s settings, on its page in your dashboard, choose:

• When it reviews: every pull request, or only when someone comments @graphide-review on it, drafts included.
• Which passes run, and the questions every review answers.
• Automatic reviews per pull request, counting the first. Unless you change it, that is one: the opening review. 0 means no limit. Past that, a push is reviewed only when someone, or their agent, comments @graphide-review.
• Comments: each review comments on the pull request, on with its reviews. You can turn comments off; the check and the review page stay.

Either way, commenting @graphide-review asks for a fresh review, and any words after it become a question the review answers. After the first review, each one covers only what changed since the last.

A pull request has no review

• The repository’s review is off: turn it on in your dashboard.
• The repository is reviewed only when mentioned: comment @graphide-review.
• The pull request used up its automatic reviews: comment @graphide-review.
• The free reviews are used up: Free reviews.
• The project lands changes without pull requests, so there is nothing to review.