What it covers
Merge Pilot does not ask people to wait: it writes the gate into the repository, so the merge button stays blocked until the change's policy is met for its latest commit.
GitHub
A ruleset requires the "Merge Pilot / change approval" check, accepted from Merge Pilot's GitHub App only. Merge Pilot reports the check on every head commit, and on merge queue commits too.
Read the docsGitLab
A protected branch and an approval rule whose only approver is the connection's bot user. Merge Pilot approves as the bot when the policy is met, and takes the approval back when it no longer is.
Read the docsNew commits and retargeting
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 docsSetup with consent
The settings written to each repository are listed per VCS, required ones and optional ones, and recorded with who agreed to them.
Read the docsWeakened protection is reported
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. New gaps are recorded in the audit log and shown on the repository.
Read the docs
See it on your own repositories
Ask for a demo on your own GitLab or GitHub repositories.

