fix(hooks): name the remedy in the blank-override failure

The hook is global and this message blocks a push, so "ECC_PYTEST_CMD is set but
names no command" left the operator holding a refusal with no next step. It now
says to point the variable at a runner or unset it to fall back to discovery,
which is the same advice the no-pytest-found branch already gives from the other
direction.
This commit is contained in:
Juan Garibay
2026-09-17 16:51:43 -04:00
parent 9cdc40e6d1
commit ca1a5ad8bc
+2 -1
View File
@@ -168,7 +168,8 @@ resolve_pytest() {
# guess. Word-split, so the command names something on PATH or an interpreter
# whose path has no spaces; a venv with spaces is found by the loop below.
read -r -a PYTEST_CMD <<<"$ECC_PYTEST_CMD" || true
[[ ${#PYTEST_CMD[@]} -gt 0 ]] || fail "ECC_PYTEST_CMD is set but names no command"
[[ ${#PYTEST_CMD[@]} -gt 0 ]] || fail "ECC_PYTEST_CMD is set but names no command.\
Point it at your test runner, or unset it to fall back to discovery."
return 0
fi
local venv