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 [image] It makes it easier for us to generate release notes. :v: See the bug definition here. ↩︎

[image] codinghorror: For those who want to bring changes to Discourse’s code, we require that each GitHub commit have one of the following prefixes: Will I18N be added to that list?

Discourse GitHub commit prefix convention

Development

Moin January 10, 2026, 9:37pm 11

Will I18N be added to that list?

Topic		Replies	Views
Better commit messages for the changelog Development	16	3275	February 5, 2016
Categorizing bug and ux issues Site feedback	17	852	August 28, 2025
Discourse Version 2.7 Announcements release-notes	3	9551	May 18, 2021
3.4.3: Bug fix and UX release Announcements release-notes	1	469	April 29, 2025
3.4.1: Bug fix and UX release Announcements release-notes	1	604	February 24, 2025

Discourse GitHub commit prefix convention

Related topics