Commit Guidelines ================= We enforce certain rules on commits with the following goals in mind: - Be able to reliably auto-generate the `CHANGELOG.md` *without* any human intervention. - Be able to automatically and correctly increment the semver version number based on what was done since the last release. - Be able to get a quick overview of what happened to the project by glancing over the commit history. - Be able to automatically reference relevant changes from a dependency upgrade. The guidelines are inspired by the [AngularJS git commit guidelines][angular-commit-guidelines]. Commit structure ---------------- Each commit message consists of a header, a body and a footer. The header has a special format that includes a type, a scope and a subject. ``` ():