Create a Merge Request

You must be a project member to create a merge request from the Merge Request page. You can't create a merge request if the branch that you want to be reviewed has any merge restrictions set or is already under review in another merge request.

Here's how to create a merge request:

1. In the left navigator, click Merge Requests .
2. Click + Create Merge Request.
3. On the Branch page of the New Merge Request wizard, in Repository, specify the Git repository.
4. In Target Branch, select or enter the branch that the review branch will be merged into.
5. In Review Branch, select or enter the name of the branch to be reviewed. If the branch doesn’t exist, it’ll be created.

   If the review branch is already under review in another merge request, the branch name won’t appear in the Review Branch list.

   Tip:

   You can use the Copy icon in the Merge Request page's top header to copy the review branch name to the clipboard.

   
   
   Description of the illustration merge-request-copy-branch-icon.png
   

   This can be useful if your repository has many branches or if the branches have long names.

6. Click Next.
7. On the Details page of the New Merge Request wizard, in Linked Issues, add issues related to the merge request.
   When you're merging branches or closing the merge request, you can mark the linked issues as resolved.
8. In Linked Builds, add jobs related to the merge request.
   Builds of the linked jobs will be run automatically whenever the review branch is updated.
9. In Tags, add project tags to associate them with the merge request.
   You can use these tags to search merge requests.
10. In Summary, enter a summary (or title) of the merge request. If one isn't specified, the default summary Merge Request for branch <review_branch_name> will be set.
11. In Reviewers, select team members and groups who’ll review the updates.

    
    Description of the illustration vbs_select_reviewers.png

    If the branch is protected, at least one default reviewer must approve the merge request. Here's what you can select:

    • To add all reviewers of the last merge request you created, select Last Used .

    • To add all the default reviewers for the protected branch, select Default Reviewers .

    • To add default reviewers individually, select each one from the list displayed. Default reviewers are identified by the Default Reviewer tag next to their name. Reviewers that aren't default reviewers can also be selected from the list and can be added individually.

      Note:

      Users in Oracle Cloud Application environments that have multiple VB Studio instances in different identity stripes have username strings that include the environment name, where that user has been defined. Since a unique user may have been defined for multiple environments, this format ensures that one identity can be distinguished from that user's other unique identities. This should help you select the correct user to add.

    • To add a group of team members, select a group that has been previously defined by your organization administrator, such as the QA group in the image. This can be quite a timesaver, especially if the group you're adding has many members.

    To remove a selection, click the X icon to the right of the selection.

12. Click Next.
13. On the the New Merge Request wizard's Description page, enter a description, and click + Create.
    You can use the project’s wiki markup to format the description.

After the merge request has been created, you're assigned the Requester role and all reviewers are assigned the Reviewer role. Email notifications are sent to reviewers informing them that they've been added as reviewers.

Note:

If you see the "E-mail address of PersonIdent must not be null" error message when you create or update a merge request, make sure that your user email address has been verified. Access your profile, verify your user email address, and retry the merge request. See Configure Your Global Email Notifications to see how to access your user profile and configure these notifications.