From 0cf23f4a53fc5dedc00ef8577a977f2f9c82978d Mon Sep 17 00:00:00 2001 From: "openclaw-docs-sync[bot]" Date: Thu, 23 Apr 2026 04:58:50 +0000 Subject: [PATCH] chore(sync): mirror docs from openclaw/openclaw@404c4c1f860568e580c9f13b1d10061c231943bb --- .openclaw-sync/source.json | 4 ++-- docs/help/testing.md | 1 + 2 files changed, 3 insertions(+), 2 deletions(-) diff --git a/.openclaw-sync/source.json b/.openclaw-sync/source.json index 1401f66cc..c99e448c9 100644 --- a/.openclaw-sync/source.json +++ b/.openclaw-sync/source.json @@ -1,5 +1,5 @@ { "repository": "openclaw/openclaw", - "sha": "112f6e16222ac896a8cb016866b96be1ab79a3dd", - "syncedAt": "2026-04-23T04:58:01.550Z" + "sha": "404c4c1f860568e580c9f13b1d10061c231943bb", + "syncedAt": "2026-04-23T04:58:49.862Z" } diff --git a/docs/help/testing.md b/docs/help/testing.md index f4687bf38..dde69cc80 100644 --- a/docs/help/testing.md +++ b/docs/help/testing.md @@ -326,6 +326,7 @@ Think of the suites as “increasing realism” (and increasing flakiness/cost): - Fast-local iteration note: - `pnpm changed:lanes` shows which architectural lanes a diff triggers. - The pre-commit hook runs `pnpm check:changed --staged` after staged formatting/linting, so core-only commits do not pay extension test cost unless they touch public extension-facing contracts. Release metadata-only commits stay on the targeted version/config/root-dependency lane. + - If the exact staged change set was already validated with equal-or-stronger gates, use `scripts/committer --fast "" ` to skip only the changed-scope hook rerun. Staged format/lint still run. Mention the completed gates in your handoff. This is also acceptable after an isolated flaky hook failure is rerun and passes with scoped proof. - `pnpm test:changed` routes through scoped lanes when the changed paths map cleanly to a smaller suite. - `pnpm test:max` and `pnpm test:changed:max` keep the same routing behavior, just with a higher worker cap. - Local worker auto-scaling is intentionally conservative now and also backs off when the host load average is already high, so multiple concurrent Vitest runs do less damage by default.