docs: require gh comment drafts · openclaw/openclaw@f2ace9f
steipete
·
2026-05-31
·
via Recent Commits to openclaw:main
| Original file line number | Diff line number | Diff line change |
|---|
@@ -148,6 +148,9 @@ Skills own workflows; root owns hard policy and routing.
|
148 | 148 | - After landing or requested close/sweep: search duplicates; comment proof + canonical commit/PR/release before closing. |
149 | 149 | - After landing/ship final: include 2-5 sentence recap of what landed: behavior change, key files/surface, proof run, issue/PR state. Do not answer with only status/links. |
150 | 150 | - `ship` that fixes an issue: after push, comment proof + commit link, then close the issue. |
| 151 | +- Public GH comments: show draft in chat first unless user explicitly asked to post/comment/reply/close/merge/land. After work starts and changes/proof exist, post the review/proof/commit comment. |
| 152 | +- Representing user: if user already has a comment/thread for the point, update/reply there when possible; avoid duplicate PR/issue comments. |
| 153 | +- No surprise GH writes: chat must mention every posted/updated public comment with URL. |
151 | 154 | - GH comments with backticks, `$`, or shell snippets: use heredoc/body file, not inline double-quoted `--body`. |
152 | 155 | - PR create: real body required. Include Summary + Verification; mention refs, behavior, and proof. |
153 | 156 | - PR create/refresh: keep PR branches takeover-ready. Use a branch maintainers can push to, or for fork PRs ensure `maintainer_can_modify` / GitHub's `Allow edits by maintainers` is enabled unless explicitly told otherwise or GitHub's Actions/secrets warning makes that unsafe. |
|
此内容由惯性聚合(RSS阅读器)自动聚合整理，仅供阅读参考。 原文来自 — 版权归原作者所有。
