commit-msg git hook prevents aborting commit

[ctorgalson]

Sometimes while starting a commit message (i.e. in git commit -v), I realize there's some reason not to commit the changes.

With the git hook in place, the commit is immediately saved when the commit file opens with no feedback of any kind. This results in confusing empty commits in the history like this (the issue id is the entirety of the commit):

This is easily corrected (if noticed immediately) with e.g. git commit --amend or git reset --soft HEAD^, but until you're used to it, it's hard to even detect it happening.

As far as I can tell, the implementation is perfectly correct (i.e. using the commit-message hook), so this may be a problem with no good solution.

[bserem]

@ctorgalson wanna try this out: https://github.com/Annertech/annertech-ddev/blob/main/scripts/git-hooks/commit-msg

I'll make a new release if you find it ok. It worked nicely for me.

NOTE: you must add the new hook file in place after you started the project, otherwise you'll get the old version again

[bserem]

This is open once again