Use the “Commits” and “Changes” tabs to confirm you’ve included the correct code.

You can complete an initial review without submitting your MR. We’ll cover them in more detail later on. These can be amended at any time using the right sidebar on the merge request details page. In general, you’ll want to note down any important changes you’ve made, as well as the reasoning behind them.Īt the bottom of the page, you’ll find controls for setting the MR’s assignee, reviewer, milestone and labels. Standards for descriptions vary by organisation and by project. Use the form to define the properties of your merge request. Find the branch you’d like to merge and click the “Merge request” button to the right of its name. Make sure you’ve pushed the changes on your local branch up to GitLab. You can create a new MR from within GitLab by navigating to Repository > Branches in the sidebar. Commercial tiers have access to additional features. We’re using the open-source GitLab CE in this article.

They combine its project management, repository and CI/CD systems into a single page for each change in your codebase. Merge Requests are one of the foundational elements of the GitLab experience. Adopting an MR-driven workflow helps you guarantee code quality by creating an expectation that all commits are thoroughly reviewed. Once you’ve reviewed your code, you can initiate the merge with a single click. A Merge Request (MR) is a wrapper around a git merge operation that’s accessible within the GitLab web UI. GitLab’s Merge Requests are your chance to review code before it enters your project’s main branch.

Git create branch gitlab