The 0.9.0 release adds a new default author-valid-email rule, important bugfixes and special case handling.
Special thanks to joshholl, ron8mcr, omarkohl, domo141, nud and AlexMooney for their contributions.
- New Rule:
author-valid-emailenforces a valid author email address. Details can be found in the
Rules section of the documentation. - Breaking change: The
--commitscommandline flag now strictly follows the refspec format as interpreted by thegit rev-list <refspec>command. This means that linting a single commit usinggitlint --commits <SHA>won't work anymore. Instead, for single commits, users now need to specificygitlint --commits <SHA>^...<SHA>. On the upside, this change also means that gitlint will now understand all refspec formatters, includinggitlint --commits HEADto lint all commits in the repository. This fixes #23. - Breaking change: Gitlint now always falls back on trying to read a git message from a local git repository, only reading a commit message from STDIN if one is passed. Before, gitlint only read from the local git repository when a TTY was present. This is likely the expected and desired behavior for anyone running gitlint in a CI environment. This fixes #40 and #42.
- Behavior Change: Gitlint will now by default ignore squash and fixup commits (fix for #33: fixup messages should not trigger a gitlint violation)
- Support for custom comment characters (#34)
- Support for
git commit --cleanup=scissors(#34) - Bugfix: #37: Prevent Commas in text fields from breaking git log printing
- Debug output improvements