Miscellaneous How-To

This page holds instructions for performing miscellaneous tasks in Gitlab.

Add Developer

Note

You can only add a developer role if you have an Owner or Maintainer role for your project.

Gitlab uses roles to manage people’s permissions in a project. Sometimes, you may need to grant someone a developer role. This most commonly occurs for code reviewers, who need a developer role to review and approve merge requests.

To add a developer to a project, navigate to the main page of the upstream repository. In the navigation sidebar, click on the Manage menu and then the Members button:

Show Button
../_images/members.PNG

Search for the person you’d like to grant a developer role. If you see the person in the list of project members, then change their max role to developer. If the person is not listed, then you will need to add them to the project. Click on the blue Invite Members button in the top right of the screen. Add the person using their email username. Set their role to Developer and click the Invite button:

Show Example
The invite member page is filled with an email address of an invited person. The role of the invited person is set to "Developer".

The reviewer should now be able to review and approve merge requests.

Create Merge Request Manually

If the merge banner does not appear, or if you want to merge a different branch, then you will need to create a merge request manually. To do so, click on the Code menu in the navigation sidebar and select the Merge Requests button:

Show Button
The navigation side is open on the "Code" menu. The "Merge Requests" button is highlighted.

Click on the blue New Merge Request button. This will open a page with options for the merge. Set the source to the review branch of your forked repository. Set the target to the main branch of the upstream repository:

Show Example
A page lists options for a new merge request. The source is set to the review branch of the forked repository. The target is set to the main branch of the upstream.

Click on the Compare branches and continue button, which will open the page for a new merge request. You can now follow the remaining instruction in the Create merge request section to finish creating the merge request.

Close Merge Request

Note

When you close a merge request, the associated code is not added to the upstream repository.

Sometimes you will need to close a merge request so that the associated code is not added to the upstream repository. This can happen when if a merge request fails a security review.

To close a merge request, navigate to the bottom of the Overview tab and click the Close merge request button.

Show button
An arrow points to the "Close merge request" button at the bottom of the merge request page.

This will close the merge request. The associated code is not added to the upstream repository, and the merge request is removed from the active merge requests tab.