tif-calin/semantic-commit-messages.md

## semantic-commit-messages.md

      
    Raw
  

              semantic-commit-messages.md
            
          
    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
! is optional. It is used when there is a BREAKING CHANGE (aka <major> in semver). Also see this discussion on what is a "breaking change". Or the FluidFramework docs
<subject> summary should be in present tense

Examples

test: Add tests for class <PeriodicPayment>

feat(landing): Add hat wobble

feat(1rm)!: Replaces formula for election validation

More <type>s

Note
Some guides restrict all messages to just feat and fix. By default you should opt to use these along with scopes and only reach for others if it really makes sense. E.g. you can use feat(docs) instead of docs)


feat: (new feature or functionality, including tests. Not necessarily user-facing)
fix: (bug fix of existing feature or functionality. Not necessarily user-facing)
style: (code-wise, not CSS! formatting, missing semi colons, renaming variables, etc) [see discussion about distinction between refactoring vs rewriting]
dev: (releases, updating grunt tasks, docker configs, deployment scripts, dependency management, etc)

What other guides suggest


joshbuchea: chore, docs, feat, fix, refactor, style, test
Here-Be-Pythons: bugs, depl, docs, feat, front, misc, perf, rfct, style, tests, ver
Angular: build, ci, docs, feat, fix, perf, refactor, style, test
JSHint: chore, docs, feat, fix, test
other: deprecate, remove, revert, wip

References


conventional commits https://www.conventionalcommits.org/
sparkbox https://seesparkbox.com/foundry/semantic_commit_messages
karma http://karma-runner.github.io/1.0/dev/git-commit-msg.html
here-be-pythons https://here-be-pythons.readthedocs.io/en/latest/git/semantic-commit-messages.html
angular https://github.com/angular/angular/blob/22b96b9/CONTRIBUTING.md#-commit-message-guidelines
understanding sem commits https://nitayneeman.com/posts/understanding-semantic-commit-messages-using-git-and-angular/
logically atomic commits https://benmatselby.dev/post/logical-commits/
jQuery https://contribute.jquery.org/commits-and-pull-requests/#commit-guidelines
cbeams https://cbea.ms/git-commit/
conventional-commit-detector https://github.com/conventional-changelog/conventional-commits-detector
atom https://github.com/atom/atom/blob/master/CONTRIBUTING.md#git-commit-messages