Semantic Commit Messages
gist.github.com · 132 words · saved by 1 readers
Semantic Commit Messages. GitHub Gist: instantly share code, notes, and snippets.
Semantic Commit Messages See how a minor change to your commit message style can make you a better programmer. Format: <type>(<scope>): <subject> <scope> is optional Example feat: add hat wobble ^--^ ^------------^ | | | +-> Summary in present tense. | +-------> Type: chore, docs, feat, fix, refactor, style, or test. More Examples: feat : (new feature for the user, not a new feature for build script) fix : (bug fix for the user, not a fix to a build script) docs : (changes to the documentation) style : (formatting, missing semi colons, etc; no production code change) refactor : (refactoring pr
related reading
- Conventional Commitsconventionalcommits.org
- How to Write a Git Commit Messagecbea.ms
- How to Write Better Git Commit Messages – A Step-By-Step Guidefreecodecamp.org
- A Note About Git Commit Messagestbaggery.com
- Writing commit messageschiark.greenend.org.uk
- Semantic Versioning 2.0.0 | Semantic Versioningsemver.org
- Keep a Changelogkeepachangelog.com
- GitHub · Change is constant. GitHub keeps you ahead.github.com
- Git from the Bottom Upjwiegley.github.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.github.com
- Using Gitcs61bl.org