MR Reviewer Handoff and Workflow
**Closed in favor of https://gitlab.com/groups/gitlab-org/-/epics/9577** <!-- triage-serverless v3 PLEASE DO NOT REMOVE THIS SECTION --> *This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.* <!-- triage-serverless v3 PLEASE DO NOT REMOVE THIS SECTION --> ## Problem to Solve Merge Request Reviewers allow users to explicitly ask people for a review of their contribution. However, when that user has finished the review there is no clear signal to the author of the merge request (absent an approval). There's also no clear signal to the reviewer when the author has addressed their feedback in the case it requires a re-review prior to the contribution being accepted. ## Proposal As part of the code review process we should provide a signaling mechanism for reviewers to indicate their review is complete or that a re-review is needed. ### What could this look like? When you've completed reviewing the merge request we could provide options to approve the MR OR approve conditionally (pending thread resolution) OR send back to author. In cases where the author needs to request another review after making the appropriate fixes, we need to add an option to re-ping (via email and To-Do) the reviewer that another review is required.
epic