Getting started with merge requests | GitLab
The Merge Request (MR) is the foundation of GitLab as a tool for code collaboration and version control.
When working on a Git-based platform, you can use branching strategies to collaborate on code.
A repository consists of its root branch, which contains a major version of the codebase, from which you create minor branches, also called feature branches, to propose changes to the codebase without committing them directly to the major version of the codebase.
Branching is especially important when working with others to prevent changes from being pushed directly to the source branch without prior checks, tests, and approvals.
When you create a new feature branch, change files, and push it to GitLab, you have the option to create a merge request, which is basically a request to merge one branch into another.
The branch you have committed your changes to is called the source branch, while the branch you want to merge your changes into is called the target branch.
The target branch can be the default or any other, depending on the branching strategies chosen.
In a merge request, in addition to visualizing the differences between the original content and your proposed changes, you can perform a significant number of tasks before completing the work and merging the merge request.
You can watch our below video for a quick overview of working with merge requests.
From the merge request list
You can create a merge request from the list of merge requests.
- On the top bar, select Menu > Projects and find your project.
- On the left menu, select Merge requests.
- In the top right, select New merge request.
- Select a source and target branch and then Compare branches and continue.
- Fill out the fields and select Create merge request.
So I hope this was very helpful and if you have any doubts or any questions you can write them down in the comment section below and I will try to answer you as soon as I can.
▬▬▬▬▬▬ Connect with me ▬▬▬▬▬▬
Our Website: https://s3cloudhub.com/