Azure DevOps Services and Server

MergeHarbor works with Azure DevOps Services (dev.azure.com) and Azure DevOps Server 2020 or later.

Azure DevOps Services

Choose Azure DevOps Services in the console and select Connect with Microsoft Entra ID. You can enter your organization URL (for example https://dev.azure.com/acme) to limit the connection to one organization; otherwise MergeHarbor can use every organization you belong to. Your organization must allow third-party application access via OAuth (Organization settings → Policies).

You can also connect with a personal access token instead.

Azure DevOps Server

Choose Azure DevOps Server, enter your collection URL (for example https://tfs.example.com/tfs/DefaultCollection), and paste a personal access token. Servers on a private network must be reachable from MergeHarbor; with self-hosted MergeHarbor, your operator allows private addresses.

Personal access tokens

Create the token for a service account with these scopes: Code (Read & write), Code (Status), Service Hooks (Read & write), and Project and Team (Read). The account needs permission to contribute to pull requests and to edit service hook subscriptions in each project; project administrators have both.

What MergeHarbor does

• Registers service hooks for the repositories you enable (pull request created and updated, pull request comments, and pushes).
• Posts findings as pull request threads on the changed lines, plus a summary.
• Reports a pull request status named mergeharbor/review. Add it to a branch policy under Status checks to require a passing review before completion.
• Learns from your feedback: liking a MergeHarbor comment, or resolving its thread as Fixed or Won’t fix.
• Replies to @mergeharbor mentions in pull request comments.