merge request
GitLab's equivalent of a pull request: a proposal to merge one branch into another, subject to review and approval.
Full Definition
A merge request (MR) is the GitLab-specific term for a code-review and merge workflow that is functionally equivalent to a GitHub pull request. It contains a diff of proposed changes, facilitates inline comments, and enforces approval rules before the merge is permitted. Editors working on documentation that spans both GitHub and GitLab workflows must apply each platform's preferred terminology within the relevant section and avoid cross-contaminating terms. 'MR' is the accepted abbreviation in GitLab-centric texts.
Usage
Usage note: Use 'merge request' exclusively in GitLab documentation. Do not substitute 'pull request' unless explicitly cross-referencing GitHub behaviour.
In Context
- "The CI pipeline must pass before a merge request can be approved and merged into `main`." — GitLab CI/CD documentation
- "Editors should verify whether the project uses GitHub or GitLab before standardising 'pull request' versus 'merge request'." — Style guide advisory