<!--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> - [Work on this issue](https://contributors.gitlab.com/manage-issue?action=work&projectId=278964&issueIid=331415) - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=331415) </details> <!--IssueSummary end--> ## 🧩 Problem statement Right now, when users enable merge train(after enabling pipeline for merged results), `Merge immediately` always shows up. Enabling pipeline must succeed only takes into account the recent pipeline(pipeline for merged results) and not the pipeline for merge train. By adding an additional toggle, users would get an option if they want the recent pipeline to be considered or specifically the pipeline for merge trains. ## ⏳ Background https://gitlab.com/gitlab-org/gitlab/-/issues/320981#note_578018148 ## 📝 Proposal This issue to provide the backend changes for https://gitlab.com/gitlab-org/gitlab/-/issues/331356 ------ - [ ] **Only allow merging via merge train** When enabled, the **Merge immediately** option is not available in merge requests. All merge requests must be added to a merge train to merge. ------ 1. Remove the line that forces 'merge immediately' to always show for merge trains 2. Add a new setting(proposed in https://gitlab.com/gitlab-org/gitlab/-/issues/331356), ensure it is persisted to the database and have relevant api endpoints for fetching and persisting the data to the servers