product-example 2 linked patterns 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.
Read with a purpose
What this source can teach
Use this source to inspect a concrete implementation and the decisions visible in its context.
- Start with the original. Open the source and find the guidance or example relevant to your task.
- Trace the connection. Use the claim notes below to see how this site applies the source to specific patterns.
- Check the setting. Compare the source's platform, people, and constraints with your own decision.
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. |
Comparisons supported by this source
- Approval workflow vs review before submit vs permission recovery vs invite user
GitLab documents required approval rules, approval counts, reviewer categories, code owners, approval status, additional approval, and revoke approval behavior.
- Human approval gate vs approval workflow vs review queue vs review before submit vs recommended next action
Supports required approvals, eligible reviewers, approval status, and revocation before merge.
Evidence Role
This source is treated as product-example evidence. Its value comes from the specific claims and setting described above.
Publisher: GitLab Docs. Last checked: .