<!--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=393578) </details> <!--IssueSummary end--> To simplify large MRs workflow we could offer an option to extract the first commit from the merge request to create a new merge request out of it. This should make a process of splitting a big MR into smaller ones a little bit easier. The whole process could look like this: 1. A big MR is created with more than 1 commit. 2. Author decides to split the MR, goes to the Commits page and clicks on the first commit and executes 'Extract into new MR' action. (design TBD) 3. A new smaller MR is created from this commit only (branch name decided during the process), target branch is re-used from the commit source MR. 4. The original MR gets a new `HEAD` that doesn't have the extracted commit and also has the target branch set to the newly created MR working branch. It also receives the newly created MR as a blocker. 5. The process repeats for the remaining commits (target branches form a chain, new MRs add up to the main MR blockers). 6. (optionally) When the extracted MR gets merged change the target branch for the original MR automatically.