Skip to content
MergeHarbor

Get started

Quickstart

Sign up, connect a code host, choose repositories, and get your first MergeHarbor review.

The console walks you through these steps with a setup checklist. Most teams finish in about five minutes.

1. Sign in

Create an account with GitHub, GitLab, Google, or Microsoft, with your work email, or through your company’s single sign-on. Accounts are linked only by email addresses that your identity provider has verified.

2. Create an organization

An organization holds your repositories, settings, members, and billing. If your company already uses MergeHarbor, ask an administrator for an invitation instead.

3. Connect a code host

Code host How you connect
GitHub, GitHub Enterprise Server Install the MergeHarbor GitHub App on the accounts and repositories you choose
GitLab, GitLab Self-Managed Connect with GitLab (OAuth), or a group or project access token
Bitbucket Cloud Connect with Bitbucket (OAuth), or a workspace, project, or repository access token
Bitbucket Data Center An HTTP access token
Gitea, Forgejo An access token
Azure DevOps Services Connect with Azure DevOps (Microsoft Entra ID), or a personal access token
Azure DevOps Server A personal access token and your collection URL

MergeHarbor registers webhooks for you and requests only the permissions it needs to read code and post reviews.

4. Choose repositories

Select the repositories MergeHarbor should review. New repositories are enabled automatically unless an administrator turns off Auto-enable new repositories.

5. Indexing

MergeHarbor builds a graph and search index of each repository in the background. Progress appears on the checklist. After the first pass, only changed files are processed.

6. Your first review

Open a pull request, or choose an open one under Review a pull request now. Reviews work before indexing finishes; the summary notes when less codebase context was available.

What a review contains

  • A summary of the change and a confidence score from 1 to 5.
  • Inline comments on the exact lines, each with severity, category, confidence, and a suggested fix where one applies.
  • A status check you can require before merging.

Next steps