Conventional Commits
A lightweight specification for commit messages written as a type, optional scope and description (feat, fix and BREAKING CHANGE footers, among others), so that changelogs and semantic version bumps can be generated automatically. Many open source projects enforce it with tools such as commitlint, so learn it before contributing to one that does. It takes ten minutes to read and makes your own history far easier to scan.
Guide
Other
Conventional Commits
10 minutes
Beginner
Free
A lightweight specification for commit messages written as a type, optional scope and description (feat, fix and BREAKING CHANGE footers, among others), so that changelogs and semantic version bumps can be generated automatically. Many open source projects enforce it with tools such as commitlint, so learn it before contributing to one that does. It takes ten minutes to read and makes your own history far easier to scan.
Ready to start?
Opens on Conventional Commits in a new tab.
Stuck on something specific?
Writing only gets you so far. If you want an answer to your situation rather than the general case, book a session and we will work through it together. Sessions are free for approved Sefism members, and a few slots open each week.
Follow along
New writing, resources and project ideas land here first.