Back to Details

full-stop

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Full Stop

Full Stop

Do the same work as 
full-send
, but stop with the PR ready for the user to merge. Never merge it.
Read full-send and follow its workflow, proof rules, review, and babysitting steps. An explicit "full stop" request authorizes that work without a separate "full send" request. That includes full-send's testing permission. A "full stop" request is the permission for the test methods Proof needs, even when a project file says to ask first, for example before computer use. Use those methods directly. Its merge permission does not apply. The overrides below take precedence.
执行与 
full-send
相同的工作，但停在 PR 已可供用户合并的状态。 绝不合并 PR。
阅读 full-send，并遵循其中的工作流、proof 规则、 审查和持续监控步骤。用户明确提出“full stop”请求，即授权执行这些工作， 无需另行提出“full send”请求。这也包括 full-send 的测试权限。 “full stop”请求授权使用 Proof 所需的测试方法，即使项目文件要求事先询问， 例如在使用 computer 前也应如此。直接使用这些方法。其合并权限不适用。 以下覆盖规则具有优先权。

No merging

禁止合并

You may commit, push, rebase, fix conflicts, and use 
--force-with-lease
on this task's branch. Never merge, enable auto-merge, enter a merge queue, push to the default branch, bypass branch protection, or delegate those actions.
Disable existing auto-merge and remove the PR from any merge queue before work begins; check again before each push. Report these changes. If you cannot prevent automatic merging, report the blocker before proceeding.
你可以在此任务的分支上 commit、push、rebase、解决冲突，并使用 
--force-with-lease
。绝不 merge、启用 auto-merge、加入 merge queue、push 到默认分支、绕过分支保护或委派这些操作。
开始工作前，禁用已有的 auto-merge，并将 PR 从所有 merge queue 中移除； 每次 push 前再次检查。报告这些更改。如果无法阻止自动合并，请在继续之前 报告阻塞原因。

Stop at the gate

停在门禁处

Use full-send's merge gate as the readiness check. Replace its merge and final report steps with a handoff. Proof and review must cover the final diff; recheck behavior changes and meaningful conflict fixes before handoff.
Fetch the target branch and check the live PR's head, base, checks, reviews, and mergeability. Confirm it is open, not a draft, and not set to merge without the user. If someone else merged it, report that instead.
  • Ready to merge: the merge gate passes. Leave the PR open and unmerged.
  • Waiting for required approval: only human approval remains. Confirm that this is the actual blocker.
  • Blocked: explain what prevents readiness, what you tried, and what is needed. Follow full-send's rules for asking the user.
In T3 Code, call 
unwatch_pull_request
before the handoff or a question. Report the PR link, final head, verdict, proof, reviewer outcome, and remaining risks. State whether the PR is still open and unmerged.
使用 full-send 的 merge gate 作为就绪检查。将其中的合并和最终报告步骤替换为 交接。Proof 和审查必须覆盖最终 diff；交接前重新检查行为变更和重要的冲突 修复。
获取目标分支，并检查实时 PR 的 head、base、checks、reviews 和 mergeability。 确认 PR 处于开放状态、不是 draft，且未设置为在未经用户同意的情况下合并。 如果其他人已合并 PR，则改为报告这一情况。
  • 可以合并： merge gate 已通过。让 PR 保持开放且未合并。
  • 等待必需批准： 仅剩人工批准。确认这确实是当前的阻塞项。
  • 已阻塞： 说明阻止就绪的原因、你尝试过的操作以及还需要什么。遵循 full-send 中询问用户的规则。
在 T3 Code 中，调用 
unwatch_pull_request
后再进行交接或提问。 报告 PR 链接、最终 head、判定结果、proof、审查者结论和剩余风险。 说明 PR 是否仍处于开放且未合并的状态。