Skip to content

[FEEDBACK] [INTERNAL] Action focused merge request homepage

This issue is for feedback on the new merge request homepage prior to a wider roll out.

Changes in Code Review Process

TLDR, Change Required: No longer remove yourself as a reviewer from a merge request once you've completed your role.

Part of the new experience for the merge request homepage expects you to stay assigned as a reviewer throughout the lifecycle of the merge request. Our aim for this new experience is to help you identify the merge requests you need to work on and what your role in them is. This means you DO NOT need to remove yourself as a reviewer upon completing your review. The new homepage will be classifying the merge requests based on events and actions within the merge request. This is a change from the traditional GitLab process, which is why we're piloting this within your team vs. broadly across GitLab.

🎗 How to give 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.

🤝 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

Edited by Michael Le