Skip to main content
By the end of this guide, DinoAI reviews every pull request (or GitLab merge request) into your production branch, posts its findings as one review, and blocks the merge while findings are open.
Prerequisites
  • A workspace with a connected dbt™ repository on GitHub or GitLab (gitlab.com or Self-Managed).
  • Code review in the sidebar of the Agent app. If it’s not there, contact Paradime support to turn it on for your company.
  • The Admin, Workspace Admin, or Workspace Settings Admin role in Paradime.
  • GitHub: an Owner of the GitHub organization, or someone who can ask one, to install the Paradime GitHub App. GitLab: an Owner of the top-level group (gitlab.com) or an instance administrator (Self-Managed), to install the GitLab connection.
Estimated time: 15 minutes.

​
Steps

1

Connect your Git provider

Open the Agent app and select Code review. If the page asks you to connect first, do it from there:
Select Install GitHub App and install the Paradime GitHub App on the repository. DinoAI posts reviews through the App. The workspace can stay on its deploy key. To do it from Settings instead, install the Paradime GitHub App.
When the provider is connected, Code review shows No reviewers yet and a New reviewer button.
2

Add a reviewer

In Code review, select New reviewer and fill in the form:
  1. Name: Production reviewer.
  2. Target branches: your production branch. The form starts with the repository’s default branch.
  3. Reviewer agent: DinoAI reviewer.
  4. When to review: Automatic, to review every pull request and each new commit.
  5. Block merging on findings: on.
  6. Select Create reviewer.
See Add a reviewer and Review modes and blocking.
3

Require the check

Block merging on findings fails the Paradime Code Review check. To stop a merge on a failed check, require it on the production branch:
In the repository’s Settings > Branches (or Rules), edit the rule for the production branch, turn on Require status checks to pass, and add Paradime Code Review. The check appears in the list after its first run.
4

Link your account

To ask DinoAI questions with @paradime in a comment, each person links their Git account to Paradime:Reviews don’t need this. Only mentions do. See Mentions.
5

Open a pull request

Open a pull request into the production branch that changes a model, for example a .sql file under models/. Within a few minutes:
  • the Paradime Code Review check shows as running, with a link to the review session;
  • a review headed DinoAI review · Production reviewer appears, with an inline comment for each finding;
  • the session shows in Code review under Recent reviews, and in Sessions with the GitHub or GitLab source.
Reply @paradime why? in a finding’s thread to ask about it.
The pull request has a DinoAI review and a Paradime Code Review check. With findings, the check fails and the merge is blocked. Push a fix, and DinoAI reviews only the new changes and clears the fixed findings. If no review appears, see Why didn’t DinoAI review my pull request?. The most common causes are a branch that no reviewer watches, and a draft pull request.

​
Next steps

End-to-end PR reviewer

A custom reviewer that also checks scope against the Linear or Jira ticket.

DinoAI Code Review

Reference: reviewers, modes, mentions, custom reviewers, and limits.

​
Troubleshooting

  • Code review says “Install the GitHub App” or “Connect GitLab”: the provider is not connected for this repository yet. Finish step 1.
  • Code review says “Code review works with GitHub and GitLab”: the repository is on Bitbucket or Azure DevOps, which Code Review doesn’t support.
  • The check never appears: the pull request may target a branch no reviewer watches, or be a draft. See Why didn’t DinoAI review my pull request?.
  • The check fails with Review budget exhausted: a DinoAI budget is used up. See Budget and consumption.