mirror of
https://github.com/conventional-commits/conventionalcommits.org.git
synced 2026-03-23 06:01:43 -05:00
Specify English as the required language for commit messages #233
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @geriwald on GitHub (Jan 24, 2026).
Summary
The Conventional Commits specification defines the structure and format of commit messages in detail, but does not explicitly state that commit messages should be written in English.
Problem
While the specification provides clear rules for types, scopes, descriptions, and footers, the language requirement is implicit. This can lead to inconsistencies in international teams or open-source projects where contributors might write commits in their
native language.
Proposal
Add an explicit rule stating that commit messages MUST be written in English, similar to how other aspects (like
BREAKING CHANGEbeing uppercase) are explicitly specified.This would:
Suggested addition
A new rule could be added:
Or alternatively, a note in the specification header clarifying this expectation.
@tats-u commented on GitHub (Feb 3, 2026):
The language of a commit message is off-topic:
Not applied to internal proprietary repositories in organizations in non-English-native countries (including France). Your suggestion is harmful because it make it harder for such organizations to adopt Conventional Commits. Not every Git user is good at English. Your own native language (e.g. French) is the most readable and clear in commit messages. If you will never make your projects public for all the tea in China, commit messages may be written in any arbitrary non-English languages, e.g. «fix(foo): suppression de l'erreur d'affichage».