Skip to main content

Change management the merge button respects

One change policy decides which checks a merge request must pass and who must approve it. GitLab or GitHub keeps the merge blocked until it is met, for the latest commit.

A closed gate in Merge Pilot's navy and orange, with six locks in its frame, and a merge request waiting in front of it.
  • Policy: passed
  • Secret scan: passed
  • Dependency scan: passed
  • Licenses: passed
  • CI: passed
  • Change approval: waiting

One merge request, from webhook to merge

  1. Merge request opens
  2. A policy covers it
  3. Checks run
  4. A change approval opens
  5. Approvers decide
  6. The gate opens for the latest commit

Every step is recorded with who did what and when, so the audit trail and the metrics come from the same place as the gate.

Merge Pilot, by CloudNativeWorks, is change management for GitLab and GitHub merge requests. A change policy decides which checks each merge request must pass and who must approve it; change approvals open in Jira or the built-in tracker, and the merge stays blocked until the policy is met for the latest commit.

  1. A merge request opens

    GitLab or GitHub tells Merge Pilot by webhook.

  2. A policy covers it

    The first active change policy that matches its branches, repository, paths, size, author or labels.

  3. Checks run

    Secrets, dependencies, licenses, CI, code review, work items and risk, as the policy asks.

  4. A change approval opens

    For changes that need one, in Jira or the built-in tracker, assigned to an approver or left to the approver pool, as the policy says.

  5. Approvers decide

    In the tracker or in Merge Pilot; never the author.

  6. The gate opens

    For the latest commit only: by default a new commit needs a new decision, unless the policy keeps the approval.

Fits the tools you already use

Integrations

GitLab (GitLab.com or self-managed) and GitHub (github.com or Enterprise Server 3.12 and newer) for code; Jira (Cloud, Server or Data Center) or the built-in tracker for change approvals; Slack, Microsoft Teams, e-mail and webhooks for notifications; OIDC, SAML and LDAP for sign-in.

All integrations

Deployment

Runs in your own infrastructure, as several instances for availability, and works in networks without internet access. Your code and your change decisions stay inside your network; package lookups can go to mirrors inside it.

Deployment

See it on your own repositories

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