Skip to main content
Set up Code Review with one repository and one ready-for-review pull request. A small first run makes it easy to verify provider access, repository scope, review output, and automation before you expand.

​
Before you start

You need:
  • Workspace access to Connectors and Code Review
  • Permission to install or authorize the GitHub, GitLab, or Bitbucket integration
  • One repository visible to the workspace
  • One non-draft test pull request
Supported providers include GitHub, GitLab, and Bitbucket, with supported self-hosted GitHub and GitLab installations.

​
Connect source control

1

Choose the provider

Open Connectors and select GitHub, GitLab, or Bitbucket.
2

Authorize a test repository

Complete the provider flow. Start with one repository when repository-level scoping is available.
3

Confirm synchronization

Open Settings → Code Management and confirm the repository appears. Reconnect or synchronize the provider if it is missing.
Codebase management with sample repositories enabled for PR review
Use the dedicated guides for Bitbucket Cloud and self-managed GitLab.

​
Enable the repository

1

Open Codebases

Go to Code Review and select Codebases → Repositories.
2

Add the repository

Select Add Repo if it is not already listed.
3

Turn on PR review

Enable PR Review, then open Show details.
4

Choose the first-run output

Start with Medium priority and above, inline comments, and a conservative comment limit. Keep automatic approval off during the pilot.
5

Save

Confirm the repository and settings, then save the change.

​
Run the first review

Open a non-draft pull request and mention the Entelligence bot with:
If automatic review is enabled, the review can also start when the pull request opens, becomes ready for review, or receives a new commit.

​
Confirm the setup works

A successful first run should:
  • Appear under Codebases → Active PRs.
  • Reference the correct repository and commit.
  • Post the selected inline or summary output.
  • Show only the enabled generated content.
  • Recognize a reply in an Entelligence thread.
  • Re-review a new commit only when Auto Review on Every Commit is enabled.
  • Respect exclusions and the configured inline-comment limit.

​
Tune the signal

After the first review is correct, tune one dimension at a time:

Review coverage

Adjust priority, comment limit, automatic triggers, and generated content.

Team context

Add guidelines, Learnings, repository Markdown, linked codebases, and exclusions.
Use a test pull request after each material change so you know which setting changed the output.

​
First-run fixes

​
Next step

Learn how to evaluate findings, or run a local review before you push.