<!--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=473054) </details> <!--IssueSummary end--> ## Problem to Solve Many integrations with GitLab around merging need to call the `/merge` endpoint. This endpoint requires a merge request to be completely ready to merge prior to being able to merge. If the merge request is not ready the endpoint returns a `422` error. The only way for a consumer to figure out what's going on is then to call the merge request API and get the `detailed_merge_status`. ## Proposal When calling the `/merge` endpoint, that should just set a merge request to auto-merge. Then when the merge request is ready, the merge will happen. If the merge request is ready to merge, then calling `/merge` will execute the existing behavior.