## Problem to solve While viewing a merge request, changes can be made to the merge request via pushes, approvals/comments, other users interacting with the merge request, pipelines completing and many other actions. These changes can impact the state of the merge request or the information that you need to review and make users lose trust in what the current state of the merge request actually is. ## Proposal Important components of the merge request should both respond in real-time and trigger updates to other relevant areas of the merge request. Areas to address: - Reviewers - Merge button widget - Approval Widget - Quick Action Changes ### Additional Details Example of how this would work in reality - as a user, when I've completed my merge request review, I should be able to leave my summary comment and click `approve this merge request`. When I do that, the approval widget should update to reflect my approval and the status of any remaining approvals. If this was the final approval needed, the merge widget should update with any remaining blockers or provide the merge button as all the requirements have been met. <!-- 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 -->