# Discourse GitHub commit prefix convention

**URL:** <https://meta.discourse.org/t/discourse-github-commit-prefix-convention/19392>\
**Category:** Development\
**Created:** [August 28, 2014, 9:32pm UTC](https://meta.discourse.org/t/discourse-github-commit-prefix-convention/19392 "2014-08-28T21:32:16Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)\
**Post date:** [August 28, 2014, 9:32pm UTC](https://meta.discourse.org/t/discourse-github-commit-prefix-convention/19392/1 "2014-08-28T21:32:16Z")

</div>

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\] |
| **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 |

 ![](https://global.discourse-cdn.com/meta/original/3X/3/c/3c2d6fdd842384af41da5ba3a1e5bae39ab88f05.png) 

It makes it easier for us to generate release notes. ✌

* * *

1. See the [bug definition here](https://meta.discourse.org/t/category-definition-for-bug/2).

---

_[View the full topic](https://meta.discourse.org/t/discourse-github-commit-prefix-convention/19392)._