A merge request (MR) is one of the core product objects, where users collaborate on proposed changes to source code. From editing, reviewing, testing, and deploying, almost everything in GitLab flows through MRs. How are MRs used in the product?
The conceptual model diagram below shows how objects, along with their attributes and actions, are related the primary merge request object. Learn more about the conceptual model.
MR attributes and actions can be embedded in related objects, like issue or pipeline.
The MR object is primarily represented in the UI using a record layout. This layout is shown below, with details about the meaning and purpose of each element. Learn more about semantic layouts.
Last updated at: