Scott

I've been thinking about this for a few days. If the issue is definitely in `git-raw-commits` then I'd rather patch the source of the bug than just patch it here?...

Given that this is fairly domain specific it's likely that a custom plugin would be the way to go. https://commitlint.js.org/#/reference-plugins If you follow the steps under `Rules in Plugins` or...

> As I wrote, would a PR be accepted to add fields to the `parsed` variable in that custom plugin function. The reason I asked is because the information I...

> I just discovered the section on plugins, would it be a good idea for me to explore this as a plugin first? This was my first thought when I...

I this true also of `type-case` and `scope-case`? They are both currently set to `lowerCase` but in theory `TYPE(scope): sUbJeCt` is a valid commit? Is the wording implying that `type`,...

I guess my point being that (ignoring the silly spongebob case) should we be enforcing `lowerCase` on `type` and `scope` or should the rule just be ignored to let the...

Agreed, I think the default config should set some standard, as you mentioned above you can tailor the plugins to behave in a certain way. I think we should enforce...

We've been having a bit of a discussion about this one in Slack and can appreciate where you are coming from. I think (internally) there is a consensus for us...

Here is my 2c for what it's worth. Forgive me because I am not sure if `[angular commit style]` is a static string or if that is contextual based on...