<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=507544) </details> <!--IssueSummary end--> ## Problem to Solve Requesting changes is a strong signal that something needs to be resolved in a merge request prior to being merged. When a user requests changes, however, if that user is unable to re-review and then approve that the new changes a merge request can be stuck. In many cases this can be resolved by having a user with `Merge` permissions click `Bypass` on the merge request, but that's not always ideal. ## Proposal We could introduce a setting similar to [`prevent merge unless all threads are resolved`](https://docs.gitlab.com/ee/user/project/merge_requests/#prevent-merge-unless-all-threads-are-resolved) which if toggled off wouldn't require a request for changes to be resolved. - This setting should be defaulted `true` so that the default behavior is requests for changes do block merging