[Design] Merge request page redesign overview

Work in progress

This is page is serve as documentation to connecting the different pieces of work around the merge request page improvements

Last key update: &13632 (comment 2949595996)

Summary

The redesign focuses on improvements that will reduce cognitive load, speed up decision-making, and make critical actions more accessible.

Main area of changes:

  1. Merge checks to the top of the Overview
    • Why:
    • What:
    • How:
  2. Unifying the approval workflow by relocating review and merge action buttons
    • Why:
    • What:
    • How:
  3. Comment management via thread panel
    • Why:
    • What:
    • How:

Impact will be measured against adoption and impact on phases of the code review cycle https://gitlab.com/groups/gitlab-org/-/work_items/20403+

Change 1: Merge checks to the top of the Overview

Moving merge checks to be the first item in the Overview content area, replacing the current description-first layout.

  • [insert issue link]

Why do we need to make the change

Addresses the following issues

What is the change

How will this change happen?

  • Immediate visibility: Users see MR status instantly without scrolling
  • Better decision-making: Clear overview of mergeability state informs next actions
  • Reduced navigation: No more hunting through variable-length content

Building upon the design proposed in work item Design review: sticky header in the MR page (#332573 - closed), this approach now addresses one of the blockers around what and how "unblock a merge" with "Set to auto-merge"

Change 2: Unifying the approval workflow by relocating review and merge action buttons

Change 3: Comment management via thread panel

Edited Jan 20, 2026 by Michael Le
Assignee Loading
Time tracking Loading