Skip to main content

Integrations

Merge Pilot works where your teams already work: it reads the VCS, writes the merge gate into it, and keeps change approvals in your tracker.

Version control

GitLab

GitLab.com or self-managed. Merge requests, pipelines and pushes by webhook; the gate is a protected branch and an approval rule whose only approver is the connection's bot user, which needs GitLab Premium or Ultimate (watching works on any tier). Members can also be allowed self-service operations through Merge Pilot, done by its bot user so people need no more GitLab rights than the minimum you set: joining projects and groups, branch protection, CI/CD variables, and project access tokens and deploy tokens (each scope capped at the person's own role). Each operation is limited to the Merge Pilot roles you choose and, except for joining, a minimum role on the repository, and every one is audited.

Read the docsSelf-service operations

GitHub

github.com or GitHub Enterprise Server 3.12 and newer, through a GitHub App created from a manifest or registered by hand. The gate is a ruleset requiring Merge Pilot's check; merge queues are supported. Through Merge Pilot, done by the App and limited per operation to the roles you choose and, except for joining, a minimum role on the repository, members can also manage CI/CD variables and secrets (repository, environment and organization), join repositories as Read, Triage or Write, and protect branches (one ruleset per protected branch, beside the gate's); every operation is audited. Joining groups, project access tokens and deploy tokens remain GitLab only.

Read the docsSelf-service operations

Change approvals

Jira

Jira Cloud, Server or Data Center. Change approvals are created from templates with your fields, assigned, and decided by moving them through your workflow.

Read the docs

Built-in tracker

A board and list inside Merge Pilot with workflows and custom fields, for teams without Jira.

Read the docs

Notifications and automation

Messages link to their page in Merge Pilot. Deliveries are queued, retried when sending fails (up to 5 attempts) and kept in a delivery log, from which they can be sent again; a delivery that fails for good is audited and announced.

Slack and Microsoft Teams

Routed by event and project path pattern, so each team hears about its own repositories.

Read the docs

E-mail

Through your SMTP server, with STARTTLS or implicit TLS; one message per recipient.

Read the docs

Personal e-mails

Assignees, authors and company admins hear about what concerns them; each person chooses their e-mails, with one-click unsubscribe.

Read the docs

Outbound webhooks

Events sent to your endpoints as JSON, signed with an HMAC-SHA256 signature the receiver checks.

Read the docs

REST API

Documented with OpenAPI, listing every endpoint an API token may call; service tokens with their own role, or personal tokens acting as their owner.

Read the docs

Sign-in

OIDC and SAML 2.0

Per company, with roles from identity provider groups. Guides for Keycloak, Microsoft Entra ID, Okta and ADFS.

Read the docs

LDAP

The company's LDAP or Active Directory, for sign-in with the directory password, limited to chosen groups and checked again when the session renews.

Read the docs

GitLab and GitHub accounts

Sign in with a VCS account of the company's connection.

Read the docs

Vulnerability and package data

OSV.dev

Vulnerabilities of dependency versions.

Read the docs

deps.dev

Licenses, publish dates and deprecation of package versions.

Read the docs

CISA KEV and FIRST EPSS

Which vulnerabilities are exploited in the wild, and how likely exploitation is.

Read the docs

OSV.dev, deps.dev, CISA KEV and FIRST EPSS can each point at a mirror for networks without internet access. The severity of CVEs that OSV.dev does not rate is looked up in NVD and CIRCL; those lookups can be turned off.

See it on your own repositories

Ask for a demo on your own GitLab or GitHub repositories.