[Design] Merge request page
Problem
It's difficult to know what needs your attention and what doesn't in GitLab, specifically around Merge Requests (e.g. moving your MRs through the process, reviewing MRs when requested). For example, at GitLab we have adopted the workaround of removing ourselves as reviewers from Merge Requests so that we don't see its number in the notification badge, and so that subsequent requests will notify us.
As stated here, GitLab should make it easy to distinguish between MRs that require your attention and MRs that don't.
- As an author (Assignee)
- Which MRs have reviewers responded to that I need to address their feedback on?
- As a reviewer (Reviewer)
- Which MRs need my review or approval?
Proposal
The current issue proposes ways to clarify who has responsibility for a merge request, whether it's a reviewer who has been requested to review, an author who needs to respond to a finished review, or a reviewer who has been re-requested to review.
Previous research/efforts