Skip to main content

How a merge request moves through Merge Pilot

Pick a scenario and watch it play: each step shows who acts, what Merge Pilot checks, what happens to the merge gate and the change approval, and what goes in the audit log.

A normal change from opened to merged: the policy decides the checks and the approvers, and the merge button follows the decision.

Merge requestOpen
Merge gateNot processed yet
Change approvalNone yet
  1. DeveloperOpens, pushes, merges
  2. GitLab or GitHubWhere the merge gate lives
  3. Merge PilotPolicy, checks, decision
  4. TrackerJira or the built-in tracker
  5. ApproversAnd admins

See it on your own repositories

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