<!--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=591125) </details> <!--IssueSummary end--> A specific combination of merge request settings causes failure to automerge, despite all checks succeeding. Specifically: if the project has 'squash commits on merge' set as required in the settings, and the automerge is enabled in the merge request, it fails with the following notification: 'This project requires squashing commits when merge requests are accepted. Try again.' Disabling the automerge and merging using the 'merge' button which then appears works, but requires a manual step in a process (enabling automerge) that is designed to be automatic. Screenshot (a 1-line change, in a single commit): {width=613 height=600} This merge request will hang until a user cancels the automerge and manually presses merge. The user has explicitly enabled automerge using the CLI push option `merge_request.merge_when_pipeline_succeeds`, yet manual action is still required to merge.