Specify English as the required language for commit messages

[geriwald]

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 CHANGE being uppercase) are explicitly specified.

This would:

• Ensure consistency across all projects following the spec
• Improve readability for international contributors
• Align with the de facto standard in the software industry

Suggested addition

A new rule could be added:

Commit messages MUST be written in English to ensure universal readability across international teams and open-source communities.

Or alternatively, a note in the specification header clarifying this expectation.

[tats-u]

The language of a commit message is off-topic:

• Improve readability for international contributors
• Align with the de facto standard in the software industry

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».