product-example checked
GitLab merge request approvals
Documents optional and required approval rules, minimum approval counts, categories of reviewers, code owners, approval status in merge requests and lists, approve additionally, and revoke approval states.
Pattern Decisions This Source Supports
| Pattern | Supported decision | Required contract | Claim note |
|---|---|---|---|
| Approval workflow | Choose approval workflow when the core job is routing a submitted request through one or more authorized decisions before work can continue. | Submitting creates a durable approval record with requester, target, requested action, version, approver rule, due date, and route state. | GitLab supports required approval rules, approval counts, reviewer categories, code owner approval, merge request approval status, additional approval, and approval revocation. |
| Human approval gate | Choose human approval gate when automation is paused at runtime and cannot execute the next step until an eligible human authorizes it. | The gate belongs to a specific automation run, step ID, payload version, model or workflow version, target object, and approver rule. | Supports eligible reviewers, approval status, required approval counts, and revocation before merge. |
Evidence Role
This source is treated as product-example evidence. Use it to validate the decision rules above, not as a visual style reference.
Publisher: GitLab Docs. Last checked: .