### Problem to solve Having markdown, [gitlab flavored markdown](https://github.github.com/gfm/) support in commit messages would encourage the writing of more informative commit messages and make reviewing commits in the process of merge request reviews easier.  ### Intended users <!-- Who will use this feature? If known, include any of the following: types of users (e.g. Developer), personas, or specific company roles (e.g. Release Manager). It's okay to write "Unknown" and fill this field in later. Developers, Reviewers, Managers * [Parker (Product Manager)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#parker-product-manager) * [Delaney (Development Team Lead)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#delaney-development-team-lead) * [Sasha (Software Developer)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#sasha-software-developer) * [Presley (Product Designer)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#presley-product-designer) * [Devon (DevOps Engineer)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#devon-devops-engineer) * [Sidney (Systems Administrator)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#sidney-systems-administrator) * [Sam (Security Analyst)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#sam-security-analyst) * [Dana (Data Analyst)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#dana-data-analyst) Personas are described at https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/ --> ### Proposal Markdown is used in several other places within gitlab. Passing a commit message through the markdown engine as the commit message web page is rendered might possibly take only a few lines of code. ### Permissions and Security This should require no additional security ### Documentation https://github.github.com/gfm/ ### Testing As this is only connecting two already existing features * display of commit messages * markdown formatting A minimal amount of additional testing should be necessary. Perhaps adding a recognition that a commit message containing markdown elements did indeed render to additional HTML. ### What does success look like, and how can we measure that? Commit messages with markdown provide a richer user experience for people reviewing commit messages in the process of code review.s ### What is the type of buyer? Developers who put effort into making informative commit messages. ### Links / references https://github.github.com/gfm/