<!--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=33431) </details> <!--IssueSummary end--> ### Problem to solve Gitlab allows a reviewer to rebase the branch of a merge request from the UI. The automatic rebase can (obviously) not re-sign GPG signed commits when doing so, but does the rebase anyway, leading to signature loss. ### Intended users * [Sasha (Software Developer)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#sasha-software-developer) ### Proposal Either disallow automatic rebasing of a branch if it contains GPG signed commits, or show a warning that this will lead to signature loss. This could be hidden behind an option, but I imagine we don't want to have 1000 different options for merge behaviour either.