Changes for version 2.3.0 - 2017-12-14

  • New features
    • The GitHooks plugin implements two new methods: get_config_boolean and get_config_integer. They're used whenever we want to get a configuration value explicitly as a boolean or an integer, following git-config's documentation about typed options. If the option's value doesn't comply with git-config's syntax specification for booleans or integers the methods croak, making clear to the user that she has a configuration error. Moreover, this allows the user to specify booleans and integers in whatever syntax they prefer, according to git-config's specification.
  • Changes
    • Notify: in the notification headers, replace 'BY:' by 'PUSHED BY:' to make it clear that we're talking about the user who pushed the commits being notified about.
    • Support Git 1.7.1, which is the version installed by default in CentOS 6. There was no code changes to make it so. We only changed the check make during the building of the module to allow the use of version 1.7.1. Previously we supported from version 1.7.2 on.
  • Fix
    • Notify: use the option i18n.commitEncoding to decode commit information before inserting it into the notifications.
    • The GitHooks::get_config method now treats the $var argument as case-insensitive, following what the git-config documentation implies.

Documentation

Modules

Framework for implementing Git (and Gerrit) hooks
Git::Hooks plugin for branch/tag access control
Git::Hooks plugin to enforce commit policies
Git::Hooks plugin for checking files
Git::Hooks plugin which requires citation of JIRA issues in commit messages
Git::Hooks plugin to enforce commit log policies
Git::Hooks plugin for checking references
Git::Hooks plugin for checking against unsafe rewrites
Git::Hooks plugin for checking whitespace errors
Git::Hooks plugin to insert a Change-Id in a commit message
Git::Hooks plugin to notify users via email
Git::Hooks testing utilities
A Git commit message
A Git::Repository plugin with some goodies for hook developers