✳flâneur — a map of the web's best reading
Conventional Commits
conventionalcommits.org · 1,535 words · saved by 4 readers
A specification for adding human and machine readable meaning to commit messages
Conventional Commits 1.0.0 Summary The Conventional Commits specification is a lightweight convention on top of commit messages. It provides an easy set of rules for creating an explicit commit history; which makes it easier to write automated tools on top of. This convention 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)] The commit contains the following structural elements, to communicate intent to the consume
Explore this link on the map →saved by
related reading
- How to Write Better Git Commit Messages – A Step-By-Step Guidefreecodecamp.org
- Writing commit messageschiark.greenend.org.uk
- How to Write a Git Commit Messagecbea.ms
- Semantic Versioning 2.0.0 | Semantic Versioningsemver.org
- CLI Reference - git-spiceabhinav.github.io
- Keep a Changelogkeepachangelog.com
- Semantic Commit Messages · GitHubgist.github.com
- Short: WiP · Rafał Pastuszaksonnet.io
- A successful Git branching model >> nvie.comnvie.com
- GitHub - conventional-changelog/conventional-changelog: Generate changelogs and release notes from a project's commit messages and metadata. · GitHubgithub.com
- commonware > Change is the Only Constantcommonware.xyz
- The comprehensive guide to writing the best PR title of all timegraphite.dev