Back to Details

w-pr

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese
Invocation requests publishing the intended branch and creating its PR. Follow git publish. The description is part of this playbook; do not use a separate generate-description step.
  1. Ensure task-owned changes are committed and validated. Use commit if needed. If this playbook must create a branch first, follow git-publish branch rules.
  2. Push the intended branch using push.
  3. Write a standalone description: problem, resulting behavior, verification evidence, and material limitations. Follow the repository template; never create an empty description. Use a conventional PR title when the repository requires it.
  4. Reuse an existing PR for this branch rather than duplicating it. Use known applicable labels and requested reviewers; do not invent assignments.
  5. With a CLI, write multiline text to a temporary file and pass the body-file option. Verify the resulting title, base, and description. Return the PR link. PR creation does not authorize merge or deployment.
调用此流程会发布目标分支并创建其 PR。请遵循 git publish。描述是此 playbook 的一部分；不要使用单独的 generate-description 步骤。
  1. 确保任务负责的更改已提交并验证。如有需要，使用 commit。如果此 playbook 必须先创建分支，请遵循 git-publish 的分支规则。
  2. 使用 push 推送目标分支。
  3. 编写一份独立描述，涵盖问题、最终行为、验证证据和实质性限制。遵循仓库模板；切勿创建空描述。如果仓库有要求，请使用 conventional PR 标题。
  4. 复用该分支已有的 PR，避免重复创建。使用已知的适用标签和指定的审查者；不要自行分配人员。
  5. 使用 CLI 时，将多行文本写入临时文件，并通过 body-file 选项传入。验证生成的标题、目标基础分支和描述。返回 PR 链接。创建 PR 不代表已授权合并或部署。