mergerequest

A merge request (MR) is a request to merge changes from one branch into another within a Git-based repository. The term is used by GitLab; GitHub and other platforms use pull requests (PRs) but the concept is the same. An MR collects the proposed changes, their description, and related information in a central place for review and integration.

The MR serves as the focal point for code review, discussion, and verification before changes become part of the main codebase. It enables collaboration by allowing contributors to propose updates, show diffs, attach issues or tasks, and solicit feedback from teammates, maintainers, or automated systems.

Typical workflow begins when a developer creates a feature or topic branch off the target branch (often main or master) and opens an MR against that target. The MR includes a description, a summary of changes, and any related issues or milestones. Reviewers are assigned, labels and priorities may be set, and continuous integration pipelines run automatically to validate the changes. New commits pushed to the source branch update the MR and retrigger checks.

During review, participants discuss the changes, request refinements, and may approve the MR. Project policies often require a certain number of approvals or passing tests before merging. When ready, a maintainer or authorized contributor merges the MR. Merge options vary by platform and may include creating a merge commit, performing a fast-forward merge, or squashing commits into a single changeset. If conflicts occur, they must be resolved in the branch, and the MR updated accordingly.

Overall, merge requests provide governance, traceability, and collaborative review around code changes before they are integrated into the main line of development.