https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38664
--- Comment #10 from David Cook <[email protected]> --- I've started to come around to the idea more after participating in the Mattermost chat, but then I realised there is 1 potential problem with the pre-commit git hook. perltidy doesn't always work. Sometimes it fails and you end up with inline error messages. For a big dev, this could be a risk. I suppose --no-verify could bypass the auto-perltidy and you could always still provide your own Tidy follow-up if perltidy is failing? Just food for thought... -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
