Skip to main content

Change requests from the pipeline, or a change policy at the merge

ServiceNow DevOps Change Velocity brings pipeline runs into ServiceNow change management: change requests are created automatically, enriched with DevOps data and approved by policy or by people. Merge Pilot decides earlier, at the merge request: one change policy runs the checks, opens the change approval in Jira or its built-in tracker, and keeps the merge blocked in GitLab or GitHub until the policy is met for the latest commit.

Side by side

The same questions, answered by DevOps Change Velocity and by a Merge Pilot change policy.

ServiceNow DevOps Change Velocity compared with Merge Pilot
TopicServiceNow DevOps Change VelocityMerge Pilot
Where the change is heldIn the pipeline. When change control is on for a pipeline step, a change request is created automatically and the pipeline is paused until it is approved. A step can use a change receipt instead, which records the change without pausing the pipeline.At the merge button. GitLab or GitHub itself keeps the merge request from merging until its change policy is met for the latest commit: an approval rule only Merge Pilot's bot user can meet on GitLab, a required check from Merge Pilot's App on GitHub.Read the docs
Pull requests and merge requestsA change approval process can be turned on for pull requests: a build starts, the approver is notified, and once the change request is approved, merging is enabled in GitHub, Bitbucket or Azure DevOps. Documented for Jenkins, GitHub Actions and Azure DevOps pipelines.Every merge request into a covered branch on GitLab or GitHub is matched to a change policy when it opens and again on every push. The gate is set by Merge Pilot's decision, so it does not wait for a pipeline to reach a step.Read the docs
Pipeline toolsChange control in pipelines from popular tools such as Jenkins, GitLab, GitHub Actions and Azure DevOps.The CI control reads GitLab pipelines, GitHub Actions workflows and the checks of GitHub Apps the policy names, on the latest commit, and can hold the merge until they pass.Read the docs
Automated decisionsChange approval policies approve a change request automatically when their conditions are met, reject it, or send it to people for manual approval. Conditions use DevOps data such as test results, code coverage and open incidents.The change type decides: standard changes merge once their checks pass, normal changes also need a change approval, emergency changes may merge first and are reviewed afterwards. The number of approvals can differ by the change's risk level.Read the docs
Data on the changeThe change request links to related lists from the connected tools, such as commits, work items, artifact versions, test summaries and security summaries.Merge Pilot runs the policy's own checks on the change (secret, dependency, license, package health, dependency source, CI configuration, container image, infrastructure and signed commits) and links the change approval to the work items named in commits, titles and branch names.Read the docs
The change recordA ServiceNow change request. Change models define its states and the rules for moving between them; the DevOps and DevOps Simplified models are active by default.A change approval in Jira or Merge Pilot's built-in tracker, created from templates with your fields. In Jira, Merge Pilot maps approved, rejected, reopened, merged and cancelled to your workflow's statuses. It does not create change requests in ServiceNow.Read the docs
Who decidesWhen a policy asks for manual approval, the users or groups who must approve are notified and decide in ServiceNow.Approvers decide in Jira, in the built-in tracker or on the merge request's page in Merge Pilot. A decision counts only when its maker may decide the change, and the author never may.Read the docs

When each fits

DevOps Change Velocity

When ServiceNow is already the change management system of record and changes are released through pipelines in several tools: change requests are created for you, carry the commits, work items, tests and security results, and changes that meet a policy's conditions can be approved automatically.

A Merge Pilot change policy

When the change to control is the merge request on GitLab or GitHub: the gate sits in the VCS itself, a new commit needs a new decision, security checks are part of the same policy, and change approvals live in Jira or in Merge Pilot's built-in tracker.

Read the docs

Both together

They act at different moments and overlap on approving changes with automated rules. A team can gate merges with Merge Pilot and still have its pipelines create change requests in ServiceNow for the deployment that follows. Merge Pilot does not open change approvals in ServiceNow; its outbound webhooks can send its events to other systems.

Read the docs

What to consider

Merge Pilot gates merge requests on GitLab and GitHub. A change that never goes through a repository, or a deployment, is outside what it sees.

See it on your own repositories

Ask for a demo on your own GitLab or GitHub repositories.

Sources

What this page says about ServiceNow DevOps Change Velocity comes from ServiceNow's documentation:

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.