Gitlint

Bugfixes

- **Behavior Change**: gitlint no longer prints the file path by default when using a `.gitlint` file. The path
will still be printed when using the new `--debug` flag. Special thanks to [Slipcon](https://github.com/slipcon)
for submitting this.
- Gitlint now prints a correct violation message for the `title-match-regex` rule. Special thanks to
[Slipcon](https://github.com/slipcon) for submitting this.
- Gitlint is now better at parsing commit messages cross-platform by taking platform specific line endings into account
- Minor documentation improvements

This release contains mostly bugfix and internal code improvements. Special thanks to
[William Turell](https://github.com/wturrell) and [Joe Grund](https://github.com/jgrund) for bug reports and pull
requests.

General
- Python 2.6 support
- **Behavior change**: merge commits are now ignored by default. The rationale is that the original commits
should already be linted and that many merge commits don't pass gitlint checks by default
(e.g. exceeding title length or empty body is very common). This behavior can be overwritten by setting the
general option `ignore-merge-commit=false`.

Features
- commit-msg hooks improvements: The new commit-msg hook now allows you to edit your message if it contains violations,
prints the commit message on aborting and is more compatible with GUI-based git clients such as SourceTree.
*You will need to uninstall and reinstall the commit-msg hook for these latest features*.

Bugfixes
- [7: Hook compatibility with SourceTree](https://github.com/jorisroovers/gitlint/issues/7)
- [8: Illegal option -e](https://github.com/jorisroovers/gitlint/issues/8)
- [9: print full commit msg to stdout if aborted](https://github.com/jorisroovers/gitlint/issues/9)
- [11 merge commit titles exceeding the max title length by default](https://github.com/jorisroovers/gitlint/issues/11)
- Better error handling of invalid general options

Development
- internal refactoring to extract more info from git. This will allow for more complex rules in the future.
- initial set of integration tests. Test gitlint end-to-end after it is installed.
- pylint compliance for python 2.7

Bugfixes

- `install-hook` and `generate-config` commands not working when gitlint is installed from pypi.

General
- Python 3 (3.3+) support!
- All documentation is now hosted on [https://jorisroovers.github.io/gitlint/]()
- **Breaking change**: exit code behavior has changed. More details in the
[Exit codes section of the documentation](https://jorisroovers.github.io/gitlint/exit_codes/).
- **Breaking change**: `--install-hook` and `--uninstall-hook` have been renamed to `install-hook` and
`uninstall-hook` respectively to better express that they are commands instead of options.

Features
- New `generate-config` command generates a sample gitlint config file
- New `--target` flag allows users to lint different directories than the current working directory
- Better error handling when gitlint is executed in a directory that is not a git repository or
when git is not installed.
- The git commit message hook now uses pretty colored output

Bugfixes
- `--config` option no longer accepts directories as value

Development
- Unit tests are now ran using py.test

Features

- Uninstall previously installed gitlint git commit hooks using: `gitlint --uninstall-hook`
- Ignore rules on a per commit basis by adding e.g.: `gitlint-ignore: T1, body-hard-tab` to your git commit message.
Use `gitlint-ignore: all` to disable gitlint all together for a specific commit.
- `body-is-missing` will now automatically be disabled for merge commits (use the `ignore-merge-commit: false`
option to disable this behavior)
- Violations are now sorted by line number first and then by rule id (previously the order of violations on the
same line was arbitrary).

Rules
- New Rule: `title-match-regex`. Details can be found in the
[Rules section of the documentation](https://jorisroovers.github.io/gitlint/rules/).

Bugfixes
- Added missing comma to setup.py which prevented pypi upload