Files
u-claw/.githooks/pre-push
zheng 46a1218fc8
Some checks failed
Tests / test (push) Has been cancelled
ci: 让测试真的跑起来(Gitea Actions + pre-push 钩子)
`node --test tests/` 在 Node 22 上根本不工作 —— Node 把路径当模块加载,
报 "Cannot find module .../tests",退出码 1,零个测试执行。而这条命令在
CLAUDE.md 里被当作标准用法记了很久。这大概就是这套断言从来没人跑起来的
一个主要原因:照文档敲,得到一个看不懂的错误。

正确形式是裸 `node --test`(自动发现 **/*.test.mjs)。四处全改,并加断言
钉住 —— 我自己第一版钩子和 workflow 也照抄了那个错误形式,实测才发现
它会无条件拦住每一次 push。

- .gitea/workflows/tests.yml:Gitea 原生位置。用 node 容器而非 setup-node,
  自建 Gitea 上后者要从 GitHub 拉,是新 runner 上又一个可能缺的东西。
  容器 tag 与 NODE_VERSION 绑定,否则 CI 测的运行时和出货的不是一个。
- .github/workflows/tests.yml:镜像一份,断言保证两边执行内容一致。
- .githooks/pre-push:不依赖任何 runner 的兜底。实测过它会拦下失败的 push。
  写明 --no-verify 怎么跳过 —— 拦不掉的钩子会被第一个被卡住的人删掉。

为什么需要钩子这一层:这台 Gitea 的 Actions 是开着的,但推上去的 workflow
产生了 0 次运行(total_count: 0),runner API 要鉴权查不了,最可能是没注册
runner。钩子是唯一完全不需要服务端支持的一层。

CLAUDE.md 补上 `git config core.hooksPath .githooks` —— 钩子是 per-clone 的,
没人替你装。
2026-08-17 18:46:53 +08:00

50 lines
2.0 KiB
Bash
Executable File

#!/bin/sh
# Runs the test suite before anything leaves this machine.
#
# This exists because CI cannot be relied on here. The suite sat unrun for the
# whole life of the upstream project — nothing invoked `node --test`, so every
# assertion in tests/ was decoration. We wired up a workflow, and on our own
# Gitea it produced zero runs, most likely because no runner is registered.
#
# A hook is not a substitute for CI: it only protects the machine it is installed
# on, and --no-verify skips it. But it is the one layer that works with no server
# support at all, and it turns "the tests exist" back into "the tests ran".
#
# Install: git config core.hooksPath .githooks
# Skip once (say the push is docs-only and node is unavailable):
# git push --no-verify
set -e
if ! command -v node >/dev/null 2>&1; then
echo "pre-push: node not found, skipping tests." >&2
echo " Run them wherever you do have node before merging." >&2
exit 0
fi
echo "pre-push: checking generated files are up to date…"
if ! node portable/lib/i18n/build-messages.mjs --check; then
echo "" >&2
echo "pre-push: generated files are stale." >&2
echo " Run: node portable/lib/i18n/build-messages.mjs" >&2
exit 1
fi
echo "pre-push: running tests…"
# Bare `node --test` discovers **/*.test.mjs. `node --test tests/` does not work:
# Node treats the path as a module to load and dies with "Cannot find module".
# That form was in CLAUDE.md for the life of the project, which is a good part of
# why nobody ever got the suite to run.
if ! node --test > /tmp/uclaw-prepush.log 2>&1; then
echo "" >&2
tail -40 /tmp/uclaw-prepush.log >&2
echo "" >&2
echo "pre-push: tests failed, push aborted." >&2
echo " Full output: /tmp/uclaw-prepush.log" >&2
echo " To push anyway: git push --no-verify" >&2
exit 1
fi
passed=$(grep -oE '^# pass [0-9]+' /tmp/uclaw-prepush.log | grep -oE '[0-9]+' || echo '?')
echo "pre-push: $passed tests passed."