Side by side
The same questions, answered by each approach.
| Topic | Separate process | Merge Pilot |
|---|---|---|
| Where the approval is enforced | The change approval is recorded in the change management system. The merge button is controlled by the VCS's own rules, such as required reviews, code owners and required checks. The merge waits for the change approval only if something brings it into the VCS, such as a check reported by an integration, or a person who looks before merging. | The gate is written into the VCS. On GitHub a ruleset requires the "Merge Pilot / change approval" check, accepted from Merge Pilot's GitHub App only; on GitLab an approval rule's only approver is the connection's bot user. The merge button stays blocked until the change's policy is met.Read the docs |
| Which changes need an approval | The VCS rules apply to a branch, or to the paths code owners cover, in the same way for every merge request. Whether a change also needs a change request is decided by the process outside the VCS. | Change policies match merge requests by target and source branch, repository, changed paths, size, author, labels and draft state. Standard changes merge once their checks pass, normal changes also need a change approval, and emergency changes may merge first and are reviewed afterwards.Read the docs |
| New commits after the approval | GitLab and GitHub can be set to remove approvals when new commits are pushed. An approved change request is tied to a particular commit only if someone records which one it covers. | A new commit needs its own decision before it can merge, and by default a fresh change approval; the policy can instead reopen the same one or keep the approval. Moving the merge request to another target branch always replaces its change approval.Read the docs |
| Separation of duties | The VCS can keep authors from approving their own merge request, and the change management system applies its own rules to its own approvals; each checks only its own records. | The author never approves their own change, known by their VCS account ID. People who committed to the change can be refused or flagged, and a decision made in Jira or the built-in tracker counts only when its maker may decide the change.Read the docs |
| Security checks | Scans run in CI or in separate tools, and the VCS can require their checks to pass. The approvers of the change request see the results if they are attached to it. | Secret, dependency, license, package health, dependency source, CI configuration, container image, infrastructure and signed commit checks are controls of the same policy, each off, reported or enforced.Read the docs |
| Evidence for an audit | The approval is recorded in the change management system; the reviews and the merge are recorded in the VCS. Evidence for a change is put together from both. | Each merge request records the policy version that decided it. The compliance report lists, for a period, the merge requests with their policy, decision, approval, scans and merge, the changes that skipped change management, and the audit trail.Read the docs |
Gaps around the gate
Direct pushes
Changes that reach a gated branch without an approved merge request, force pushes and deleted branches are reported as violations.
Read the docsWeakened protection
Gated repositories are checked every few hours for what would let a change skip the gate, such as an unprotected branch, force pushes, an edited approval rule or a ruleset bypass.
Read the docsWhat to consider
Changes outside merge requests
Merge Pilot gates merge requests on GitLab and GitHub. A change that never goes through a repository is outside what it sees.
VCS editions
On GitLab the gate's approval rule needs GitLab Premium or Ultimate; watching works on any tier. On GitHub, github.com or GitHub Enterprise Server 3.12 and newer.
IntegrationsYour tracker
Change approvals are created in Jira Cloud, Server or Data Center from templates with your fields, or in the built-in tracker for teams without Jira.
Read the docsTry it without blocking
Repositories can be watched first: merge requests are evaluated and recorded, nothing is blocked, and the monitoring report shows what change management would have held.
Read the docsSee it on your own repositories
Ask for a demo on your own GitLab or GitHub repositories.
