<!--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=19647) </details> <!--IssueSummary end--> ## Problem to Solve When [reverting a commit or merge request](https://docs.gitlab.com/ee/user/project/merge_requests/revert_changes.html) in GitLab a branch is created to perform the revert that is named `revert-COMMIT_SHA`. This branch may not match organizational policies for branch names or conflict with project configured push rules. ## Proposal GitLab should provide an optional project level configuration that allows the revert branch naming methodology to be set to meet organizational needs. ### Additional Details Some items to consider: 1. It could be considered to implement a variable/template system similar to [commit template variables](https://docs.gitlab.com/ee/user/project/merge_requests/commit_templates/#supported-variables-in-commit-templates) 2. Should branches be prepended or apended with `revert` (not editable by users) to make it clear that the branch is a revert 3. Could this leverage push rule configuration?