<!--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=209944) </details> <!--IssueSummary end--> This would be a configuration option at the Project level with three impacts: - Automatically fill in the Merge Request summary text from the first commit message in the MR - Automatically keep the MR summary text in sync with commit message updates when new pushes occur. - If the MR summary is changed, merging that MR should result in the commit message being automatically updated in the landed commit. There are a few different feature requests buried in here and making things work in all scenarios is hard. E.g. you can’t update summaries automatically if there are multiple commits / commit messages. And what do you do when a change was made in both the commit message and the MR summary? This is mostly targeted at Gerrit fans. Gerrit doesn't have a separate concept of a MR summary: since each review unit is a commit, they use the commit message as the summary when rendering the review. Requested by a [large prospect](https://gitlab.my.salesforce.com/00161000004bZKw). /cc @jramsay