Semantic Commit Messages

Structured format for writing Git commit messages: `<type>(<scope>): <subject>`. It explains that using specific types like `feat`, `fix`, or `docs` in the message makes the commit's purpose clear and improves programmer communication. The guide notes that the scope is optional and that the subject should be written in the present tense.

See how a minor change to your commit message style can make you a better programmer. Format: <type <scope : <subject <scope is optional 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 production code, eg. renaming a variable test : adding missing tests, refactoring tests; no production code change chore : updating grunt tasks etc; no production code change References: