vernonthedev / git-commit-naming-conventions Goto Github PK

Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)

#Build: Comment goes here

Changes to CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)

#CI: Comment goes here

Changes which doesn't change source code or tests e.g. changes to the build process, auxiliary tools, libraries

#Chore: Comment goes here

Documentation only changes

#Docs: Comment goes here

A new feature has been added

#Feat: Comment goes here

A bug fix

#Fix: Comment goes here

A code change that improves performance

#Perf: Comment goes here

A code change that neither fixes a bug nor adds a feature

#Refactor: Comment goes here for refactoring

Revert something

#Revert: Comment goes here

Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)

#Style: Comment goes here

Adding missing tests or correcting existing tests

#Test: Comment goes here

Separate subject from body with a blank line, 
Limit the subject line to 50 characters
Capitalize the subject line
Do not end the subject line with a period
Use the imperative mood in the subject line
Wrap the body at 72 characters
Use the body to explain what and why vs. how