commit c05b8b2883468606920ec63f057bf07cccd1f614
author Masaya Suzuki <draftcode@gmail.com> Mon Oct 31 13:06:35 2022 -0700
committer Masaya Suzuki <draftcode@gmail.com> Sun Feb 05 01:48:59 2023 +0000
tree ec161a236ffb0d64e1a5bef56327a496ba184ecd
parent 12ab14dca318beb58c0473c7b29d6978de09bba0

Detect empty messages with a cutoff

Git includes additional information when "git commit --cleanup=scissors"
or "git commit --verbose" is used. This includes a marker line that Git
detects and strips out the messages after that.

When this option is used, the commit-msg hook couldn't detect if the
commit message is empty properly. This change teaches the hook about the
cutoff line.

This shouldn't interfere with the existing behavior. With
I633e5db4643851376422f839d969094043abb5c5, this "git stripspace"
invocation is used purely for the message emptiness check. The actual
end result should still contain the scissors as tested in
commit-msg_test.sh.

Note that this part is prone to the pipefail problem. However, this
script's shebang is /bin/sh, not Bash, and it's not as trivial as
setting 'set -o pipefail'. Since other parts of the script already use a
pipe, this issue would be orthogonal to this change.

Change-Id: Idd4d6e5cd00e7114e0cac26f8f508602fdce39c0
Release-Notes: The commit-msg hook respects the scissors marker for the empty message detection.