# Better commit messages for the changelog

**URL:** https://meta.discourse.org/t/better-commit-messages-for-the-changelog/39107
**Category:** Development
**Created:** [February 5, 2016, 5:37pm UTC](https://meta.discourse.org/t/better-commit-messages-for-the-changelog/39107 "2016-02-05T17:37:44Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![jomaxro](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jomaxro/32/126216_2.png) [@jomaxro](https://meta.discourse.org/u/jomaxro)
#### Post date: [February 5, 2016, 5:41pm UTC](https://meta.discourse.org/t/better-commit-messages-for-the-changelog/39107/2 "2016-02-05T17:41:47Z")

</div>

Did you check out the pinned #Development topic?

> [@Discourse GitHub commit prefix convention](https://meta.discourse.org/t/new-github-checkin-prefix-convention/19392):
>
> For those who want to bring changes to Discourse’s code, we require that each GitHub commit have one of the following prefixes: Prefix Definition FIX A bug fix [[1]](#footnote-70985-1) PERF A performance improvement UX A user interface change SECURITY A security problem fix FEATURE An added feature A11Y An accessibility improvement I18N Translation updates MT Changes to migrations tooling DEV A Discourse internals change that doesn’t belong in the above categories It makes it e…

There already is a convention in place. Whether it is used…that’s a different issue.

---

_[View the full topic](https://meta.discourse.org/t/better-commit-messages-for-the-changelog/39107)._