Use Angular’s commit message convention
  • Updated on 22 Apr 2019
  • 1 minute to read
  • Contributors
  • Share
  • Dark
    Light

Use Angular’s commit message convention

  • Share
  • Dark
    Light

This rule validates every commit message and ensures they adhere to the Angular commit message convention.

Use case(s)

  • 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.

3x-17d0e50-Screen_Shot_2019-01-16_at_19.58.34.png

How to fix?

  1. Fix the errant commit message
  2. Datree's policy check automatically ensures commit messages adhere to the Angular commit message convention


What's Next

Activate a policy
Was this article helpful?