<!--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=18142) </details> <!--IssueSummary end--> ## Problem to solve If I make a typo in a commit message, or want to improve the detail of my commit messages, I need to go back to my local machine to make these changes. The only escape hatch that GitLab provides is squash and merge, but I don't have merge permissions, so I need to rely on someone else fixing my commit message during the sqush. But this assumes I want to squash my commit messages! ## Further details At GitLab we use Danger to validate commit messages after pushing, but as a developer working on a WIP merge request the only way to do that is to leave GitLab and fix it offline. It should be possible to resolve it in the interface. A concern with making rewriting history on the server easy, is that it requires any other collaborator understand they'll need to rebase their feature branch on the remote feature branch. ## Proposal As a developer working on a merge request, I will be able: - open the commit list - click edit and reword all the commit messages in my branch that are in my branch :warning: Merge requests are not only used by feature branches, like merging from release branch to release branch. If the **Source branch** is protected, this feature should be disabled. ## How will we measure success? ## Links / references