On-demand validation about commitplease

[alisianoi]

I have taken a closer look at grunt-commitplease

Currently, our commit-msg-hook.js uses the fact that it is either in node_module/commitplease or .git/hooks directory, so it can just go two levels up and get the .git/COMMIT_EDITMSG file. So, it can be run standalone with node node_modules/commitplease, like we do for jQuery Core. That will check the latest .git/COMMIT_EDITMSG (only the latest one) or fail if project history is empty.

So, I think here is what should happen. The instance of commit-msg-hook.js that gets copied to .git/hooks needs to get extra "check .npmrc for nohook" logic. The other instance that stays inside node_modules should get extra "let the user select a larger range of commits" logic (like in grunt-commitplease).

Tell me what you think, I am a bit confused how to do that at the moment.

[alisianoi]

I'd say 2.7.x solves both the "validating commit range" and "better using .npmrc/package.json to skip hook"