Development record
In .githooks/commit-msg, a top-level line 'if git rev-parse -q --verify MERGE_HEAD >/dev/null 2>&1; then' placed after the hook's RS004 setup made the guard's script reading block the hook's later '"$go_bin" build -buildvcs=false -o "$work/abcd" ./cmd/abcd' line as kill-by-holder (a program name from a command substitution reading as a refused command), where the hook without that line reads as a warn only. The same if without the redirection, or the check read into a variable first, reads as before; a six-line script holding only go_bin, that if and the build is allowed, and respelling is_scissors without && inside [[ ]] does not clear it, so the earlier context that triggers it is not isolated.
In .githooks/commit-msg, a top-level line 'if git rev-parse -q --verify MERGE_HEAD >/dev/null 2>&1; then' placed after the hook's RS004 setup made the guard's script reading block the hook's later '"$go_bin" build -buildvcs=false -o "$work/abcd" ./cmd/abcd' line as kill-by-holder (a program name from a command substitution reading as a refused command), where the hook without that line reads as a warn only. The same if without the redirection, or the check read into a variable first, reads as before; a six-line script holding only go_bin, that if and the build is allowed, and respelling is_scissors without && inside [[ ]] does not clear it, so the earlier context that triggers it is not isolated.
Frontmatter
| id | iss-2610262219399974 |
|---|---|
| type | issue |
| lifecycle | open |
| severity | minor |
.abcd/work/issues/open/iss-2610262219399974-in-githooks-commit-msg-a-top-level-line.md
open on GitHub ↗ · commit history ↗