A specification for adding human and machine readable meaning to commit messages

Nitai Charan

Community Picks is a section on daily.dev where our community members share the most interesting and valuable content they've discovered online. From insightful articles to handy tools, every post is a gem curated by our dedicated coomunity. To contribute to Community Picks, you need to have at least 250 reputation points, ensuring that only active and trusted members can share their finds.

Community Picks

The Conventional Commits specification is a lightweight convention for commit messages that provides easy rules for creating an explicit commit history. It introduces types such as 'fix' and 'feat' to represent bug fixes and new features, respectively. Breaking changes can be indicated using a footer with 'BREAKING CHANGE'. The specification allows additional types and footers, and is not case-sensitive except for 'BREAKING CHANGE'.

Conventional Commits

If you want to know more about semantics for commit messages,
check out this resource: <a href="https://gist.github.com/joshbuchea/6f47e86d2510bce28f8e7f42ae84c716" target="_blank" rel="noopener nofollow">https://gist.github.com/joshbuchea/6f47e86d2510bce28f8e7f42ae84c716</a>.

Examples can be found in commits from big projects as <a href="https://github.com/angular/angular/commits/main" target="_blank" rel="noopener nofollow">Angular Core</a> and <a href="https://github.com/nestjs/nest/commits/master" target="_blank" rel="noopener nofollow">Nest.JS Core</a> using the Git Commit Convention.
Another help would be asking ChatGPT or any other artificial intelligence chatbot to give example of commits scopes.

Using commit patterns helps a lot to keep a readable and understandable history, especially thinking about the future!

Just follow the angular commit method