docs: require fresh autoreview before landing code · openclaw/openclaw@fbc611a
steipete
·
2026-06-01
·
via Recent Commits to openclaw:main
| Original file line number | Diff line number | Diff line change |
|---|
@@ -128,7 +128,7 @@ Skills own workflows; root owns hard policy and routing.
|
128 | 128 | - Full suites, broad changed gates, Docker/package/E2E/live/cross-OS proof, or anything that bogs down the Mac: Crabbox/Testbox. |
129 | 129 | - One/few files local. If a local command fans out, stop and move broad proof to Crabbox/Testbox. |
130 | 130 | - Before handoff/push: prove touched surface. Before landing to `main`: issue proof plus appropriate full/broad proof unless scope is clearly narrow. |
131 | | -- Pre-land/pre-commit code changes: use `$autoreview` until no accepted/actionable findings remain, unless equivalent manual review already done, trivial/docs-only, or user opts out. If findings want refactor, refactor; no ugly fixes. |
| 131 | +- Pre-land/pre-commit code changes: mandatory fresh `$autoreview` until no accepted/actionable findings remain. Do not land code on CI, ClawSweeper, prior review comments, or your own manual review alone unless user explicitly opts out or scope is truly trivial/docs-only. If findings want refactor, refactor; no ugly fixes. |
132 | 132 | - If proof is blocked, say exactly what is missing and why. |
133 | 133 | - Do not land related failing format/lint/type/build/tests. If unrelated on latest `origin/main`, say so with scoped proof. |
134 | 134 | - Docs/changelog-only and CI/workflow metadata-only: `git diff --check` plus relevant docs/workflow sanity; escalate only if scripts/config/generated/package/runtime behavior changed. |
|
此内容由惯性聚合(RSS阅读器)自动聚合整理，仅供阅读参考。 原文来自 — 版权归原作者所有。
