Side by side
The same questions, answered by GitHub's own rules and by a Merge Pilot change policy.
| Topic | GitHub rulesets and branch protection | Merge Pilot |
|---|---|---|
| Where the merge is held | Rulesets and branch protection rules hold merges into the branches they target: a required pull request, approving reviews, required status checks and more. Several rulesets can apply to one branch, and the most restrictive version of each rule applies. | A ruleset named "Merge Pilot change management" requires the check "Merge Pilot / change approval", accepted only from Merge Pilot's GitHub App. The check succeeds for the latest commit once the change policy is met; a new push has no check until Merge Pilot decides on it.Read the docs |
| Who must approve | A required number of approving reviews from people with write access, optionally including a review from code owners. | The policy lists ways to approve, for example 1 of Security and 2 of Operations, from the project's approver roles, an approver pool or the code owners of the changed files. The number of approvals can differ by risk level.Read the docs |
| Code owners | A CODEOWNERS file names the people or teams responsible for paths. GitHub requests their review automatically, and a rule can require a code owner's approval; when a line names several owners, an approval from any one of them is enough. | A "Code owners of the changed files" requirement reads the CODEOWNERS file on the target branch and asks one approval from each set of owners. Owners are people: teams named in the file are not asked.Read the docs |
| Which pull requests need what | Rulesets target branches by name or pattern, in one repository, or at organization level across many repositories. | Change policies match pull 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 |
| Required checks | Required status checks must pass before merging, and a required check can expect a chosen GitHub App as its source, so the same check reported by anyone else does not count. Rules can also require successful deployments, signed commits and code scanning results. | The CI control counts GitHub Actions workflows and the checks of GitHub Apps the policy names. 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 |
| New commits after an approval | Stale approvals can be dismissed when new commits change the pull request's diff. | A new commit needs its own decision and, by default, a fresh change approval; the policy can instead reopen the same one or keep the approval. The code review control counts approving reviews on the latest commit only.Read the docs |
| Separation of duties | A rule can require the most recent push to be approved by someone other than the person who pushed it. | The author never approves their own change. By default people who committed to it may not approve (a policy can flag them instead), and an approver who merges the change can be flagged.Read the docs |
| Merge queue | A merge queue tests each queued pull request together with the changes ahead of it, and waits for the required checks to be reported on the merge group before merging. | When a pull request enters the queue, Merge Pilot reports its check on the merge group's commit: success only when change management approved the pull request at the commit it was queued with.Read the docs |
| Bypass | A ruleset's bypass list lets chosen roles, teams or GitHub Apps bypass its rules. | Bypass actors that an administrator added to Merge Pilot's ruleset are kept, and the setup warns how many there are; the protection check can report them. An urgent fix can go through an emergency policy instead: it may merge first and is reviewed afterwards.Read the docs |
When each fits
GitHub's rules on their own
When what you need is review by the right people and passing checks, GitHub does it where developers already work, with no second system: rulesets layered across branches and repositories, code owner review, checks bound to the App that reports them, and a merge queue that keeps a busy branch green.
A Merge Pilot change policy
When a merge also needs a recorded change approval, when what a change needs depends on more than its target branch (paths, labels, size, risk, the type of change), when security checks belong to the same decision, or when an audit asks which policy version let each merge through.
Read the docsBoth together
They overlap on reviews, code owners and required checks. Merge Pilot's ruleset is one ruleset among yours and does not touch the others; GitHub applies them all, so the reviews, code owner review and other checks you already require stay in force, with the change approval added as one more required check.
Read the docsWhat to consider
Merge Pilot works with github.com and with GitHub Enterprise Server 3.12 and newer, as a GitHub App. Watching repositories, which records what change management would have done without blocking anything, writes nothing to them.
Read the docsSee it on your own repositories
Ask for a demo on your own GitLab or GitHub repositories.
Sources
What this page says about GitHub comes from GitHub's documentation:
- GitHub Docs: About rulesets
- GitHub Docs: Available rules for rulesets
- GitHub Docs: About protected branches
- GitHub Docs: About code owners
- GitHub Docs: Managing a merge queue
Product details as of November 2026; check the vendor's documentation for changes.
All product names and trademarks belong to their respective owners. Their use here identifies the products and implies no endorsement.
