Support commit body and footer

One or more footers MAY be provided one blank line after the body. Each footer MUST consist of a word token, followed by either a :<space> or <space># separator, followed by a string value (this is inspired by the git trailer convention).

A footer’s token MUST use - in place of whitespace characters, e.g., Acked-by (this helps differentiate the footer section from a multi-paragraph body). An exception is made for BREAKING CHANGE, which MAY also be used as a token.

A footer’s value MAY contain spaces and newlines, and parsing MUST terminate when the next valid footer token/separator pair is observed.

Breaking changes MUST be indicated in the type/scope prefix of a commit, or as an entry in the footer.

If included as a footer, a breaking change MUST consist of the uppercase text BREAKING CHANGE, followed by a colon, space, and description, e.g., BREAKING CHANGE: environment variables now take precedence over config files.

---

“Support” means completion for the BREAKING CHANGE token is available in the right contexts, as per specification.

The : (colon) character will be automatically inserted and the caret will be placed one space after it.

[notbear]

@lppedd Works as a charm. Well done, thanks!

[lppedd]

@notbear btw, now that I handle body, footer type and footer value differently I’m open to integrations such as with Github Issues