Skip to main content

Block a merge until the Jira change approval is approved

· 11 min read
The team behind Merge Pilot

A change approval in Jira only matters if the merge waits for it. When the approval lives in one system and the merge button in another, a merge request can merge while its ticket is still open, or merge a commit nobody approved. This guide explains how Merge Pilot ties the two together on GitLab and GitHub, and what happens on the detours: new commits, a new target branch, a rejection and an emergency.

GitHub change management beyond required reviews

· 9 min read
The team behind Merge Pilot

Required pull request reviews are where most GitHub teams start with change control. Rulesets, required status checks, CODEOWNERS and merge queues take it further, and together they can make a protected branch hard to change without review. What they do not provide by themselves is a change approval: a decision made in the organisation's change process, recorded in a tracker, and enforced at the merge button. This guide covers the GitHub features first, then shows where a change approval fits.

GitLab change management: approval rules and beyond

· 8 min read
The team behind Merge Pilot

GitLab ships with a solid set of controls for merge requests: protected branches, approval rules, code owners, merge checks and external status checks. For many teams they are enough. Organisations that run formal change management usually need a little more: a change approval in a tracker, different paths for different kinds of change, and evidence that ties it all together. This guide describes what GitLab offers natively, then what a Merge Pilot change policy adds and how the two fit together.

Mapping ITIL change types to merge requests

· 9 min read
The team behind Merge Pilot

ITIL sorts changes into three types: standard, normal and emergency. Each type has its own path to approval, and most change management processes in larger organisations are built on that split. Merge requests rarely are. This guide shows how to carry the three change types over to GitLab and GitHub merge requests with change policies, so a documentation fix, a production release and a hotfix each follow the path meant for it.

Separation of duties on merge requests: what auditors check

· 10 min read
The team behind Merge Pilot

Separation of duties on code changes sounds simple: the person who writes a change should not be the one who approves it. In practice an audit asks more than that. Who else touched the change, who merged it, whether the approval in the ticket was made by someone allowed to make it, and whether the rules themselves could be loosened by one person. This guide walks through those questions and shows what Merge Pilot enforces and what it records for each.