Glossary
The words the documentation uses, in alphabetical order, each with the page that explains it.
Advisory check
A background check, every 24 hours by default, that looks the dependencies recorded for each project up again for new vulnerability advisories, without reading the repositories. See Vulnerability tracking.
API token
A token that lets a program call the REST API without a browser session: a service token acts for the company with its own role, a personal token as the person who made it. See API tokens.
Approval fatigue
A warning raised when one approver approves as many change approvals as the company's threshold within a number of days. It never blocks. See Approval fatigue guard.
Approver pool
A named group of people, such as a change advisory board or a security team, that a change policy can ask approvals from. See Approver pools.
Approver roles
The repository roles (in GitLab or GitHub) whose holders may approve a change when the policy names no pool. Set per VCS connection, and per repository. See VCS connection settings → Approver roles.
Audit log
The record of who did what and when, including what Merge Pilot did by itself. Entries cannot be edited or deleted. See Audit log.
Baseline
A project's first analysis. It sets the starting point of the project's vulnerability inventory: nothing it finds counts as new or is announced. See Project analysis.
Bot user
The GitLab account a GitLab connection works as. It is the only approver of the approval rule that forms the merge gate, so Merge Pilot approves a merge request as this account once its policy is met. See GitLab.
Built-in tracker
The issue tracker inside Merge Pilot (MergePilot Tracker), an alternative to Jira for change approvals and work items. See Tracker.
Bulk operation
Watching, moving to change management, moving back to watching or stopping watching many repositories at once, in the background. See Bulk operations.
Catch-all policy
The policy at the bottom of each VCS connection's list. It has no conditions and covers every merge request no other policy matches; a new connection's catch-all refuses everything. See Change policies.
Change approval
The tracker issue that records the decision on one change. Approvers approve or reject it, in the tracker or in Merge Pilot; the author never decides it. See Change approval lifecycle.
Change calendar
A company's change freezes and change windows, and the Insights view that shows them. See Change calendar.
Change freeze
A period on the change calendar when merges are held (Hold merges), only emergency changes may merge (Emergency changes only), or every change is scored critical risk (Raise risk only). See Change freezes.
Change management
The mode of a repository whose merges Merge Pilot enforces: the merge gate is written to the repository and merges wait for the policy. The other mode is watching. See Change management.
Change policy
The rules for one kind of change: which merge requests it covers, its change type and its controls. The first active policy that matches a merge request decides it. See Change policies.
Change type
How a policy has its changes approved: normal (approved before the merge), standard (pre-approved), emergency (reviewed after the merge), or Refuse (nothing it covers may merge). See Change types.
Change window
A time of the week when changes are expected. Changes outside every window get a higher timing score in their risk. See Change windows.
Clearance track
The five stages shown for each merge request (Policy, Checks, Change approval, Approved, Merged) with where it stands. See Merge requests.
Code owners
The owners of the changed files, as the repository's CODEOWNERS file names them. A policy can ask them to approve. See Code owners.
Company
A tenant in Merge Pilot, with its own connections, repositories, policies, people and settings, isolated from other companies. See Companies.
Company directory
A company's own LDAP or Active Directory, whose people sign in with their directory user name and password. See Company directory (LDAP).
Connection
A link from a company to an outside system: a VCS connection to GitLab or GitHub, or a tracker connection to Jira or the built-in tracker. See Connections.
Control
One check a policy runs on a merge request, such as work items, CI, the secret scan or the change approval. Each is off, reported (shown, does not hold) or enforced (holds the merge until it passes). See Controls.
Direct change
A change that reached a watched branch without a merge request: a direct push, a force push or a deleted branch. It is a Violation under change management and Would have been blocked on a watched repository. See Direct changes.
Emergency change
A change that may merge as soon as its checks pass, and is reviewed afterwards within the policy's review deadline. See Emergency changes.
EPSS
The Exploit Prediction Scoring System from FIRST: the probability that a vulnerability is exploited in the next 30 days, shown as EPSS N%. A company can hold merges from a chosen percentage. See Exploited in the wild, and likely to be.
Exception
A recorded decision to accept a known vulnerability for a limited time, or to mark it as not affecting you. While it is in force, the vulnerability does not hold merge requests and shows as Accepted. See Vulnerability exceptions.
Finding
One advisory affecting one package version on one project's default branch, in the vulnerability inventory. A secret scan's results are also called findings. See Vulnerability inventory.
Four-eyes review
A company setting that makes changes to the controls themselves (policies, approver pools, risk settings, sign-in and others) wait until a second administrator approves them. See Governance tab.
Grace period
How long Merge Pilot keeps working after its license expired: 14 days unless a platform admin sets 0 to 90. See Platform settings → Grace period.
Head check
A regular comparison of each watched branch's head with the last one seen, to find direct changes whose push event was missed. See Branch head check.
Identity provider
A company's OpenID Connect or SAML 2.0 single sign-on service (Keycloak, Entra ID, Okta, AD FS and others) that its people sign in through. See Identity providers.
Job
A unit of background work, such as processing a merge request, a scan or opening a change approval. Jobs are retried when they fail. See Jobs.
KEV
CISA's Known Exploited Vulnerabilities catalog. A vulnerability in it is marked Exploited (KEV): attackers use it now. A company can let such a vulnerability count as critical. See Exploited in the wild, and likely to be.
Lockout
After too many failed password sign-ins for one user name from one address, that address may not sign in to the account for a while. A company's password policy can make it stricter. See Failed sign-ins.
Merge gate
How GitLab or GitHub itself keeps a merge request from merging until its policy is met: on GitLab an approval rule only the bot user can meet, on GitHub the required check Merge Pilot / change approval. Its states are Can merge, Waiting and Blocked. See Merge gate.
Merge request
A GitLab merge request or a GitHub pull request. The documentation says merge request for both. See Merge requests.
Monitoring report
What change management would have done to the merge requests of watched repositories over a period, by policy and by project. See Monitoring report.
Normal change
A change whose change approval must be approved before it may merge. See Change types.
Out of scope
A merge request moved to a target branch that change management does not cover. It is no longer gated, and an undecided change approval is cancelled. See Moved to another target branch.
Periodic re-check
Merge Pilot's regular pass, every 10 minutes by default, over open merge requests that are still waiting: it reads back what lost webhooks would have said, retries what failed, and evaluates them again. See The periodic re-check.
Project
A repository of a VCS connection that Merge Pilot knows about, either watched or under change management. See Repositories.
Project analysis
A read of a project's whole default branch: its dependency manifests, dependencies, known vulnerabilities and licenses. The vulnerability inventory and the SBOM are built from it. See Project analysis.
Resync
The merge request page's action that reads CI and the change approval again from the VCS and the tracker, retries what failed, and evaluates the merge request again. See Resync.
Risk hold
A merge held because its risk level reaches the level the policy holds from, until someone allowed to accepts the risk. See How the hold works.
Risk score
A number from 0 to 1 for each merge request, from the company's risk settings: when the change is made, how critical the service is, what kind of files it touches and how large it is. It gives the risk level (low, medium, high, critical). See Risk.
SBOM
A software bill of materials: the list of dependencies a project's default branch uses, with their licenses, exported as CycloneDX 1.7 or SPDX 2.3 JSON. See SBOM export.
Separation of duties
Rules on who may approve a change besides its author: whether people who committed to it may approve, and whether an approver may merge it. See Separation of duties.
Stand-in
A colleague who approves in an approver's place while they are away, for a set period. See Stand-ins for approvers.
Standard change
A pre-approved change: it merges once its checks pass, with no change approval unless one is kept as a record. See Standard changes.
Status comment
The one comment Merge Pilot keeps up to date on a merge request under change management: whether it can merge, and the state of each control. See The status comment.
Target branch
A branch whose merge requests Merge Pilot follows: the company's branch patterns, or the project's own. See Branch patterns.
Vulnerability inventory
For each project, the known vulnerabilities its default branch depends on, since when, and which change brought each in. See Vulnerability inventory.
Watched
The mode of a repository that Merge Pilot only records: it decides each merge request as change management would, but writes nothing to the repository and holds nothing. See Watching repositories.
Work item
The tracker issue a change was made for, such as PAY-123, referenced in the merge request's commit messages, title, description or branch name. See Work items.