Skip to content

A team of long-lived bots for DeepSeek Harness, with main bots, bot-to-bot messages and group chats.

Ask fork PR authors to keep Allow edits from maintainers enabled

Fei2411c5280bd70f66
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 42e5b4aa..f735ae00 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -56,7 +56,7 @@ An issue that spans several areas, or none, gets no area label.
### Pull requests
-1. Open the pull request into `dev` and fill in the template. Link the issue with `Fixes #<number>`; a bug fix always names the bug it fixes.
+1. Open the pull request into `dev` and fill in the template. Link the issue with `Fixes #<number>`; a bug fix always names the bug it fixes. When opening a pull request from a fork, keep **Allow edits from maintainers** turned on so that the maintainer can resolve conflicts or make small adjustments before merging.
2. Write one sentence about what users will notice in the **Changelog** field of the template, or "none". Do not edit `CHANGELOG.md`: the maintainer writes it from these sentences at release time.
3. When CI passes, merge it yourself with **Create a merge commit**, then delete the branch. A review is not required; if you want one, ask a teammate in the pull request.
4. A fix that is merged into `dev` does not close its issue: `Fixes #<number>` acts only on the default branch. The issue stays open until the release, which means "fixed in `dev`, not released yet".
diff --git a/CONTRIBUTING.zh.md b/CONTRIBUTING.zh.md
index 8eb8b322..ff92c93c 100644
--- a/CONTRIBUTING.zh.md
+++ b/CONTRIBUTING.zh.md
@@ -56,7 +56,7 @@
### Pull Request
-1. 向 `dev` 提 Pull Request,按模板填写。用 `Fixes #<号>` 关联 Issue;修 bug 的 PR 一定要写明修的是哪个 bug。
+1. 向 `dev` 提 Pull Request,按模板填写。用 `Fixes #<号>` 关联 Issue;修 bug 的 PR 一定要写明修的是哪个 bug。从 fork 提 Pull Request 时,请保持勾选 **Allow edits from maintainers**,方便维护者在合并前解决冲突或做小调整。
2. 在模板的 **Changelog** 一栏写一句用户能看到的变化,没有就写「无」。不要改 `CHANGELOG.md`:维护者发版时根据这些句子统一写。
3. CI 通过后,自己用 **Create a merge commit** 合并,然后删除分支。不强制审查;想让人看一眼,在 Pull Request 里 @ 队友。
4. 合进 `dev` 的修复不会关闭对应的 Issue:`Fixes #<号>` 只在合入默认分支时生效。Issue 会一直开着,直到发版,意思是「已在 `dev` 修复,尚未发版」。