Use Angular’s commit message convention
This rule validates every commit message and ensures they adhere to the Angular commit message convention.
- Trigger automatic build and publish processes (for example, semantic releases, generating CHANGELOG, etc.)
- Ability to explore a more structured commit history makes it easier for users to contribute to a project
- Inform teammates, the public, and stakeholders regarding code changes
When does this rule fail?
A commit in the pull request does not adhere to the Angular commit message convention.
How to fix?
- Fix the errant commit message
- Datree's policy check automatically ensures commit messages adhere to the Angular commit message convention
|Activate a policy|
Was this article helpful?