The Conventional Commits specification provides an easy set of rules for creating an explicit commit history, which makes it easier to write automated tools on top of. It dovetails with SemVer, by describing the features, fixes, and breaking changes made in commit messages. The commit message should be structured as follows: <type>[optional scope]: <description> [optional body] [optional footer(s)]. Additional types are not mandated by the Conventional Commits specification, and have no implicit effect in Semantic Versioning (unless they include a BREAKING CHANGE). A scope may be provided to a commit’s type, to provide additional contextual information and is contained within parenthesis. The specification also includes examples of commit messages with different types, scopes, and footers, as well as multi-paragraph bodies and multiple footers. The Conventional Commits specification is available in multiple versions and languages including English, Italian, Polish, Chinese, Spanish, Russian, Japanese, French, Korean, Portuguese, Indonesian, Armenian, German, Thai, Ukrainian, Belarusian, Dutch, and Malayalam.
