@ceejbot @nexdrew fork of angular's commit format that lifts the restrictions on commit message size. I'm of the opinion that this is the right thing to do, and I'm building an opinionated library!
This will allow us to annotate our commits with feat:, fix:, feat: BREAKING CHANGE:, but other than that we can have as verbose and descriptive of commit messages as we desire.
Coverage remained the same at 100.0% when pulling 94cc14b75813b068e1ad5b960031e7be12aa689b on bcoe:standard-style into 354466bbf0abe0d6e26569a4f5879ee90f273da1 on conventional-changelog:master.
@ceejbot @nexdrew fork of angular's commit format that lifts the restrictions on commit message size. I'm of the opinion that this is the right thing to do, and I'm building an opinionated library!
This will allow us to annotate our commits with
feat:
,fix:
,feat: BREAKING CHANGE:
, but other than that we can have as verbose and descriptive of commit messages as we desire.