Skip to main content

FAQ

Short answers, each with the page that has the details. Words in bold are explained in the Glossary.

Platforms and setup​

Can we use GitLab and GitHub at the same time?​

Yes. A company can have several VCS connections of each provider, for example two GitLab instances and one GitHub organization, and each connection has its own change policies. GitLab works as GitLab.com or self-managed; GitHub as github.com or GitHub Enterprise Server 3.12 or newer. See Connections.

Which GitLab and GitHub plans do we need?​

Repositories under change management on GitLab need GitLab Premium or Ultimate, because the merge gate is an approval rule. On GitLab.com, creating project access tokens through Merge Pilot also needs Premium or Ultimate. On GitHub, rulesets on private repositories need GitHub Team (or Pro) or Enterprise. Repositories that are only watched need neither. See GitLab and GitHub.

Do we need Jira?​

No. Change approvals and work items can live in Jira (cloud, Server or Data Center) or in the built-in tracker. A normal change does need a tracker of either kind linked to its VCS connection; without one it cannot be approved. Standard changes need no tracker. See Built-in tracker and Jira.

Can several teams or business units share one Merge Pilot?​

Yes. Each company is a tenant with its own connections, repositories, policies, people and settings, isolated from the other companies. See Core concepts.

What does Merge Pilot change in our repositories?​

Nothing for a watched repository on GitHub, and one project webhook on GitLab. For a repository under change management: on GitLab, protected target branches, the bot user as a member, one approval rule per target branch and the project webhook (plus two optional approval settings); on GitHub, one ruleset named Merge Pilot change management. You see each step and agree to it before it is written. See Change management.

Watching and change management​

What is the difference between watched and change management?​

A watched repository is only recorded: Merge Pilot decides each merge request as its policy would, but writes nothing and holds nothing. Under change management the decision is enforced: the merge gate holds the merge until the policy is met, a change approval is opened when the policy needs one, and a status comment explains what is missing. See Repositories → The two modes.

Can we try it out before enforcing anything?​

Yes. Watch the repositories first, optionally importing their past merge requests, and read the monitoring report (Insights → Monitoring): what change management would have done with their merge requests under the current policies, by policy and by project. Then move the repositories to change management one by one or in bulk. See Watching repositories and Monitoring report.

What happens to open merge requests when a repository moves to change management?​

You choose: either only new merge requests and new commits are gated, and the open ones pass until their next commit, or the open ones are gated at once. See What happens to the open merge requests.

Approvals​

Can the author approve their own change?​

No, never: not in Merge Pilot and not by moving the change approval in the tracker. Merge Pilot undoes such a move and records it. By default, people who committed to the change may not approve it either, and a policy can flag or forbid an approver merging the change. See Separation of duties.

Where do approvers approve?​

In Merge Pilot, with Approve and Reject on the merge request page, or in the tracker by moving the change approval to its approving or rejecting status. Both count the same, and one person counts once. See Approving and rejecting.

Who may approve a change?​

Whoever the policy asks for: people holding the repository's approver roles, the members of an approver pool such as a change advisory board, or the code owners of the changed files, in the number the policy sets, which can grow with the risk level. An approver who is away can have a stand-in. See Approval.

What about urgent fixes?​

An emergency change merges as soon as its checks pass, even during a change freeze that lets emergencies through, and is reviewed afterwards within the policy's review deadline (72 hours by default). Who may declare an emergency, and how often per repository, can be limited. See Emergency changes.

What if someone merges around Merge Pilot?​

Merging cannot be stopped from outside the VCS, so a merge that bypassed the gate is recorded and flagged: merged without approval, during a change freeze, or against separation of duties, with a notification. Changes pushed to a watched branch without a merge request are recorded as direct changes. See What is flagged at merge and Direct changes.

Can one administrator weaken the controls alone?​

Not when four-eyes review is on: changes to policies, approver pools, risk settings, sign-in, the company directory, identity providers and vulnerability exceptions then wait until a second administrator approves them. See Governance tab.

Operations​

What happens to merges if Merge Pilot is unavailable?​

They wait. On GitLab, a merge request merges only with the bot user's approval, and on GitHub only with Merge Pilot's required check, so nothing new can be approved while Merge Pilot cannot answer. A merge request that already had the gate open for its latest commit keeps it. A new commit closes it again until Merge Pilot decides: on GitHub the new commit has no check yet, and on GitLab the setup step Remove approvals when commits are added (on by default) removes the bot's approval. Watched repositories are not affected. When Merge Pilot is back, the periodic re-check reads what it missed for the merge requests it knows, and a merge request it never saw is picked up at its next event. See Merge gate and The VCS or the tracker is unavailable.

What if GitLab, GitHub or Jira is down?​

Work is retried automatically, and the periodic re-check recovers lost events afterwards. A scan that cannot read the merge request fails, never passes. A vote cast in Merge Pilot while the tracker is down still counts; the tracker is updated later. See What happens when….

Does Merge Pilot hold merges during change freezes?​

Yes, when the company sets a freeze to Hold merges (or Emergency changes only) on its change calendar. Approvals go on during the freeze, and the gate opens again after it ends. See Change calendar.

Does it work with merge queues and merge trains?​

Yes. On GitHub, Merge Pilot answers the merge queue's check and passes only pull requests approved at the commit they were queued with. On GitLab, pipelines of merged results and merge trains count for the CI control. See Merge queues and merge trains.

Can people manage variables or branch protection without VCS rights?​

Yes. Merge Pilot does these operations (CI/CD variables, branch protection, GitLab project access tokens and deploy tokens, joining repositories, change management) with its own account on the VCS: the GitLab bot user or the GitHub App. It offers only what people's own VCS role does not allow; what they can already do on the VCS, such as forking or creating branches, they do there. For each operation a company admin chooses which Merge Pilot roles may ask for it and the minimum role the person must hold on the repository, for example Developer on GitLab to manage variables. Every operation is recorded in the audit log with who asked and the rule that allowed it. A token's value is shown once to the person who created it and never stored. See VCS connection settings.

What happens to access people got through Merge Pilot when they leave?​

Merge Pilot records the repository and group access people give themselves by joining through it, and the tokens it creates. When someone leaves the company or unlinks their VCS account, a repository is removed from Merge Pilot, a connection is deleted or a company deactivated, Merge Pilot never takes that access away on the VCS on its own: it lists it for company admins under Company → People, to check and remove on the VCS (or revoke a token from there), then dismiss. See People.

Why can't people manage pipeline schedules through Merge Pilot?​

To change a GitLab pipeline schedule, Merge Pilot's account would have to take its ownership, and GitLab runs a scheduled pipeline with its owner's permissions. A Developer could then have pipelines run with the rights of Merge Pilot's account, which are more than their own. Merge Pilot offers only what people's own role does not allow and never what would weaken change management for anyone but company admins. See VCS connection settings.

Which release of Merge Pilot are we running?​

The release is shown at the bottom of the sidebar to everyone who is signed in. An API token can read it from GET /api/v1/version.

Security and data​

Does Merge Pilot keep the secrets it finds?​

No. A secret finding records the rule, the file, the line and the severity; the secret itself is never stored or shown, and never written to the merge request comment. See Secret scan.

How long is data kept?​

What Merge Pilot keeps, and for how long:

DataKept
Audit logThe company's Keep audit log entries for (days): 365 by default, 30 to 3,650 (the platform's own entries: 365 days). Nobody can edit or delete an entry
Fixed vulnerabilities, ended exceptions, details of older analyses, direct changesThe company's Keep fixed vulnerabilities, old analyses and direct changes (days): 365 by default, 30 to 3,650. Open and accepted vulnerabilities are always kept
Completed and failed background jobs7 days
Notification deliveries7 days

See Audit log, Scanning → Vulnerability tracking, Jobs and Delivery log and failures.

How do people sign in?​

With a Merge Pilot password, the company's LDAP directory, an OpenID Connect or SAML 2.0 identity provider (Keycloak, Entra ID, Okta, AD FS and others), or their GitLab or GitHub account. The platform decides which methods companies may use, and each company turns on the ones it needs. See Sign-in.

Can we automate with an API?​

Yes. The REST API accepts service tokens, which act for the company with their own role, and personal tokens, which act as their person. See API tokens.

How do we show an auditor what happened?​

The Auditor role reads everything in the company and changes nothing. The audit log records who did what, including what Merge Pilot did by itself, and the compliance report exports a period's merge requests, changes outside change management and audit entries as CSV or PDF. See Compliance report and Roles and users.