What it covers
For a change that needs one, Merge Pilot opens a change approval in the company's tracker, assigns it to someone who may decide it (or leaves it to the whole approver pool, if the policy says so) and counts the decisions, made in the tracker or in Merge Pilot.
Approver pools and ways to approve
A policy lists one or more ways to approve; each lists requirements, such as 1 approval from Security and 2 from Operations. Any one way met approves the change.
Read the docsCode owners
A requirement can ask the people the CODEOWNERS file on the target branch names for the changed files: one approval from each set of owners, with GitLab sections and their counts honoured.
Read the docsApprovals by risk
A requirement can ask for a different number of approvals at each risk level of the change.
Read the docsNever the author
The author is known by their VCS account ID, so renaming the account does not help. People who committed to the change can be kept from approving it, or flagged.
Read the docsTracker decisions are checked
A decision made in Jira or the built-in tracker counts only when its maker may decide the change. An approval is withdrawn only by such a person or an administrator; anyone else's move is undone.
Read the docsStand-ins
An approver who is away can hand their seat to a stand-in for a period, within the rules the company sets.
Read the docsEmergency rules
Who may declare an emergency, whether the author may, and how many emergencies a repository may have in a period are company settings a policy can override. Every declaration is recorded and announced.
Read the docsApproval fatigue
When turned on, one person approving many change approvals within a set number of days is flagged. It warns; it blocks nothing.
Read the docs
See it on your own repositories
Ask for a demo on your own GitLab or GitHub repositories.

