Features
--------

- From now you can define which commands will be executed in pre commit and pre
  push hooks generated by `peltak git add-hooks`.
- git-flow commands now support hooks. All commands have pre- and post- hooks
  (pre-release-start, post-release-start, pre-task-merged, post-task-merged
  etc.)
- Scripts now support attaching the script directly to the root CLI (the peltak
  command). This can be achieved with root_cli: True script config option.
- script commit configuration option now also accepts strings. If string is
  given it is treated as glob pattern and only staged files that match this
  glob will be injected into the template.
- Support for custom project scripts. This is a more advanced feature and has
  the potential of deprecating a lot of existing peltak functionality. Needs a
  bit more testing on various projects. This allows the user to create custom
  bash like scripts that leverage jinja2 templates. It is very flexible for a
  lot of cases and the ones it doesn't cover can be handled using custom
  commands. This makes peltak flexible and extensible on every level.
- Initial implementation of hooks. This is an experimental API and might change
  without any notice. The documentation will be included as part of the main
  docs once the code matures.

Changes
-------

- From now on, when the patch version component is 0 it will also be used. So
  version 0.25 becomes 0.25.0. This is more consistent and intuitive.
- Rename script config value from commit to only_staged. Seems more descriptive
  and intuitive.
- lint, test, docs, docker push and docker build commands were deprecated in
  favor of using scripts functionality of peltak. Those commands will be kept
  for one full minor version cycle so projects can have time to migrate from
  them to scripts. The will be removed with another minor version bump.
- From now on, the codebase will be checked for type errors using mypy.
- Documentation has been slightly updated and docs build warnings were
  resolved.
- Remove support for pelconf.py. It has been supported alongside pelconf.yaml
  for quite a while now and is almost never used anymore as we can just write
  any python module and reference it from pelconf.yaml.