Skip to content
MergeHarbor

Code hosts

GitLab and GitLab Self-Managed

Connect GitLab.com or a self-managed GitLab instance to MergeHarbor with OAuth or an access token.

  1. In the console, choose GitLab (or GitLab Self-Managed and enter your instance URL).
  2. Authorize MergeHarbor on GitLab.
  3. Choose the projects to review.

MergeHarbor stores the tokens encrypted, refreshes them automatically, and registers a webhook on each project you enable.

For self-managed instances, your administrator can register an OAuth application for MergeHarbor (scope api, redirect URL shown in the console) or enter an existing application’s ID and secret when connecting.

Connect with an access token

Use a group or project access token with the Developer role or higher and the api scope. Group tokens cover every project in the group. Choose Connect with a token and paste it; MergeHarbor verifies the token and stores it encrypted.

How reviews appear

Reviews are posted as merge-request discussions positioned on the diff, with a summary note and a commit status. Comments that GitLab cannot position on the diff are listed in the summary.

Webhook events used: merge request, comments, and push.

Private networks

Instances that are not reachable from the internet need a self-hosted MergeHarbor deployment inside your network.