The intention of out commit-msg hook was to enforce the use of conventional commits. However the commit-msg is too strict and in a way limits our commit messages. From the specs: An optional scope MAY be provided after a type. A scope is a phrase describing a section of the codebase enclosed in parenthesis, e.g., fix(parser): Currently the scope is not optional for this project. Sometimes a scope may not be necessary and it may overly complicate our commit message or repeat itself for the sake of fulfiling the scope. Types other than feat and fix MAY be used in your commit messages. These are the only types that we allow in our commit messages which limits how descriptive we can be. There are several more we can add to make our commit messages more concise:
- build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
- ci: Changes to our CI configuration files and scripts (example scopes: Circle, BrowserStack, SauceLabs)
- docs: Documentation only changes
- feat: A new feature
- fix: A bug fix
- perf: A code change that improves performance
- refactor: A code change that neither fixes a bug nor adds a feature
- style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
- test: Adding missing tests or correcting existing tests
|