GitLab Duo in merge requests

  • Tier: Ultimate with GitLab Duo Enterprise - Start a trial
  • Offering: GitLab.com
This page contains information related to upcoming products, features, and functionality. It is important to note that the information presented is for informational purposes only. Please do not rely on this information for purchasing or planning purposes. The development, release, and timing of any products, features, or functionality may be subject to change or delay and remain at the sole discretion of GitLab Inc.

GitLab Duo is designed to provide contextually relevant information during the lifecycle of a merge request.

Generate a description by summarizing code changes

History

When you create or edit a merge request, use GitLab Duo Merge Request Summary to create a merge request description.

  1. Create a new merge request.

  2. In the Description field, put your cursor where you want to insert the description.

  3. On the toolbar above the text area, select Summarize code changes ( tanuki-ai ).

    Above the text area, a toolbar displays a “Summarize code changes” button.

The description is inserted where your cursor was.

Provide feedback on this feature in issue 443236.

Data usage: The diff of changes between the source branch’s head and the target branch is sent to the large language model.

Have GitLab Duo review your code

History

The availability of this feature is controlled by two feature flags. For more information, see the history.

This feature is considered experimental and breaking changes may still be made to this feature.

When your merge request is ready to be reviewed, use GitLab Duo Code Review to perform an initial review:

  1. On the left sidebar, select Search or go to and find your project.
  2. Select Code > Merge requests and find your merge request.
  3. In a comment box, enter the quick action /assign_reviewer @GitLabDuo, or assign GitLab Duo as reviewer.

Provide feedback on this feature in issue 517386.

Data usage: When you use this feature, the following data is sent to the large language model:

  • Contents of the file
  • The filename

Interact with GitLab Duo in reviews

You can mention @GitLabDuo in comments to interact with GitLab Duo on your merge request. You can ask follow-up questions on its review comments, or ask questions on any discussion thread in your merge request.

Interactions with GitLab Duo can help to improve the suggestions and feedback as you work to improve your merge request.

Summarize a code review

History

When you’ve completed your review of a merge request and are ready to submit your review, use GitLab Duo Code Review Summary to generate a summary of your comments.

  1. On the left sidebar, select Search or go to and find your project.
  2. Select Code > Merge requests and find the merge request you want to review.
  3. When you are ready to submit your review, select Finish review.
  4. Select Add Summary.

The summary is displayed in the comment box. You can edit and refine the summary prior to submitting your review.

Provide feedback on this experimental feature in issue 408991.

Data usage: When you use this feature, the following data is sent to the large language model referenced above:

  • Draft comment’s text

Generate a merge commit message

  • Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
  • LLM: Anthropic Claude 3.5 Sonnet
History

When preparing to merge your merge request, edit the proposed merge commit message by using GitLab Duo Merge Commit Message Generation.

  1. On the left sidebar, select Search or go to and find your project.
  2. Select Code > Merge requests and find your merge request.
  3. Select the Edit commit message checkbox on the merge widget.
  4. Select Generate commit message.
  5. Review the commit message provided and choose Insert to add it to the commit.

Data usage: When you use this feature, the following data is sent to the large language model:

  • Contents of the file
  • The filename