Ultimate customer here: <!-- This template is a great use for issues that are feature::additions or technical tasks for larger issues.--> ### Proposal As a basic example, look at the most recent commit to gitlab https://gitlab.com/gitlab-org/gitlab/-/commit/d0d366cac2fc34ac374b3efd5cc712f9ff97e3c5 . At the end of the commit it says > See merge request gitlab-org/gitlab!52429 However, if you use the [Squash and Merge](https://docs.gitlab.com/ee/user/project/merge_requests/squash_and_merge.html) feature in GitLab, while you can edit the squashed message, it is a tad annoying to put "See merge request" at the end of the squashed message. And more importantly, if someone FORGETS to edit their squashed commit message before merging, then the reference to the MR will not be included. This proposal suggests an option to automatically append "See merge request ---" to the end of squashed commit messages. Related to https://gitlab.com/gitlab-org/gitlab/-/issues/26748 Related to https://gitlab.com/gitlab-org/gitlab-foss/-/issues/53269 Related to https://gitlab.com/gitlab-org/gitlab-foss/-/issues/49013 Related to https://gitlab.com/gitlab-org/gitlab/-/issues/21686 Related to https://gitlab.com/gitlab-org/gitlab-foss/-/issues/49010 <!-- Use this section to explain the feature and how it will work. It can be helpful to add technical details, design proposals, and links to related epics or issues. --> <!-- Consider adding related issues and epics to this issue. You can also reference the Feature Proposal Template (https://gitlab.com/gitlab-org/gitlab/-/blob/master/.gitlab/issue_templates/Feature%20proposal.md) for additional details to consider adding to this issue. Additionally, as a data oriented organization, when your feature exits planning breakdown, consider adding the `What does success look like, and how can we measure that?` section. -->