<!--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=404947) </details> <!--IssueSummary end--> In https://gitlab.com/gitlab-com/gl-infra/production/-/issues/8608 some users were experiencing 500 errors after rebasing their MRs when their projects had the `Remove all approvals` setting on. The user flow that caused the 500 errors (to be confirmed): 1. Create project -> Remove all approvals setting on (this may be default) / FF merge on 1. Create MR (ensure target has at least one more commit than source) 1. Approve MR 1. Rebase <- this never completes and this is where the 500 occurs 1. ~~Check approval removed (may have to wait 10s and refresh as removing approvals is async)~~ 1. ~~Approve MR~~ 1. Check approval NOT removed as it is a rebase 1. Merge There are two scenarios where this can occur based on the following settings: 1) Remove all approvals 2) Remove approvals of Code owners This issue is to ensure we are covering this scenario with either feature specs or an E2E test. Incident: - https://gitlab.com/gitlab-com/gl-infra/production/-/issues/8608+ - https://gitlab.com/gitlab-com/gl-infra/production/-/issues/8670+