docs: 团队版本管理章节 / Team Version Management chapter#12
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
There was a problem hiding this comment.
Pull request overview
Adds a new Team Version Management documentation chapter and wires it into the existing agent version-control docs and glossary in both Chinese and English.
Changes:
- Adds a full new team-level version management guide for Chinese and English docs.
- Adds navigation from individual Agent version control to team version management.
- Adds glossary entries for team version management, member locking, and team releases.
Reviewed changes
Copilot reviewed 6 out of 6 changed files in this pull request and generated 4 comments.
Show a summary per file
| File | Description |
|---|---|
docs/02-user-guide/06-agents/09-team-version-management.md |
New Chinese chapter for team version management workflows. |
i18n/en/docusaurus-plugin-content-docs/current/02-user-guide/06-agents/09-team-version-management.md |
English mirror of the new chapter. |
docs/02-user-guide/06-agents/08-version-control.md |
Adds next-step navigation to the new team chapter. |
i18n/en/docusaurus-plugin-content-docs/current/02-user-guide/06-agents/08-version-control.md |
Adds matching English navigation. |
docs/05-more/03-glossary.md |
Adds Chinese glossary definitions for team version terms. |
i18n/en/docusaurus-plugin-content-docs/current/05-more/03-glossary.md |
Adds matching English glossary definitions. |
Comments suppressed due to low confidence (1)
docs/05-more/03-glossary.md:149
- The Chinese glossary consistently formats translated headings with full-width parentheses, e.g.
Teach（教）andTool（工具）. This new heading uses ASCII parentheses instead, so please align it with the established glossary format.
### Team Release(团队发布)
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| 5. 标注是否为私有仓库 | ||
| 6. 保存 | ||
|
|
||
| 保存后,系统会自动把团队的当前状态作为一次发布,等你下次推送时同步到远端。 |
Comment on lines
+146
to
+149
| ### Team Member Lock(团队成员锁定) | ||
| 团队对每位成员智能体的精确版本指向。即使成员智能体在自己的仓库里继续迭代,团队默认仍指向锁定的版本,保证别人下次安装时能装到一模一样的组合。需要同步到成员最新版本时,使用"升级成员"操作。 | ||
|
|
||
| ### Team Release(团队发布) |
Comment on lines
+143
to
+151
| ### Team Version Management（团队版本管理） | ||
| 把整支智能体团队当作一个整体进行版本管理的能力,包括组织变化(加成员/换队长/解散)的自动记录、推送到 GitHub/Gitee 远程仓库、发布团队新版本、从他人链接一键 Fork 安装等。与单个智能体的版本管理是两层独立体系。 | ||
|
|
||
| ### Team Member Lock(团队成员锁定) | ||
| 团队对每位成员智能体的精确版本指向。即使成员智能体在自己的仓库里继续迭代,团队默认仍指向锁定的版本,保证别人下次安装时能装到一模一样的组合。需要同步到成员最新版本时,使用"升级成员"操作。 | ||
|
|
||
| ### Team Release(团队发布) | ||
| 为团队打一个完整的版本号(例如 v0.1.1)、生成变更日志、并同步到远程。发布后这个版本可以被分享、回退、或作为参考点。 | ||
|
|
Comment on lines
+143
to
+151
| ### Team Version Management | ||
| The ability to manage an entire Agent team as a single versioned unit — automatic recording of organizational changes (add member / change leader / disband), pushing to GitHub/Gitee remotes, releasing new team versions, one-click forking from someone else's link, and more. Independent from individual Agent version management. | ||
|
|
||
| ### Team Member Lock | ||
| The team's precise version pointer to each member Agent. Even as a member Agent keeps iterating in its own repository, the team continues to point at the locked version by default — guaranteeing that anyone installing the team later gets the exact same combination. Use "Upgrade Members" to sync to members' latest versions. | ||
|
|
||
| ### Team Release | ||
| Stamping a complete version number (e.g., v0.1.1) on the team, generating a changelog, and syncing to the remote. Once released, the version can be shared, reverted to, or used as a reference point. | ||
|
|
4 tasks
New chapter explains how a whole team can be versioned, pushed to GitHub/Gitee, released to the community, and one-click installed from someone else's link — written in the same mentor-style, customer-facing voice as the existing single-Agent Version Control chapter. Changes: - New docs/02-user-guide/06-agents/09-team-version-management.md (zh-Hans, main source) - New i18n/en/.../09-team-version-management.md (English mirror) - 08-version-control.md "Next steps" links to the new chapter (zh + en) - Glossary adds 3 entries: Team Version Management / Team Member Lock / Team Release (zh + en) Covers, in plain-language customer voice: - Why a team needs versioning - Two-layer model (team-level vs member-level) - 4 member sources (local / git / marketplace / built-in core) - Connecting a remote repo (GitHub/Gitee) - Viewing history, push/pull, upgrading members, releasing a new version - Installing from someone's link (forking) - Disband-as-archive (recoverable) - 5 common scenarios Build verified: pnpm build passes for both zh-Hans and en locales, no broken links. Related to desirecore PR #656.
1. 09-team-version-management.md line 64: replace "as a release" wording with "as a commit" — the remote-config step records a snapshot, the actual release flow is documented separately later. 2. Glossary: change ASCII parentheses to full-width parentheses on the two new Team entries, matching the rest of the zh-Hans glossary format (Teach（教）, Tool（工具）...). 3. Glossary (zh + en): reorder the three new Team entries alphabetically — Team Member Lock → Team Release → Team Version Management — so the T section stays navigable. 4. English 09 Next Steps: re-add the link to Intelligent Task Orchestration now that PR #14 has merged the English translation of that concept page.
yi-ge
force-pushed
the
feat/team-version-management
branch
from
d750c19 to
bd17ea0
Compare
Member
Author
|
Thanks @copilot-pull-request-reviewer — addressed all 4 review comments + re-added a link that was previously stripped due to a missing English translation. Pushed bd17ea0:
Bonus:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
概述 / Summary
新增"团队版本管理"章节,补全客户文档站对团队级 git 协作能力的覆盖。
Adds a Team Version Management chapter to cover the team-level git collaboration features the customer docs were missing.
改动 / Changes
docs/02-user-guide/06-agents/09-team-version-management.mdi18n/en/.../09-team-version-management.mddocs/02-user-guide/06-agents/08-version-control.mdi18n/en/.../08-version-control.mddocs/05-more/03-glossary.mdi18n/en/.../05-more/03-glossary.md内容覆盖 / Coverage
延续
08-version-control.md的导师式、客户向语气,完全避免技术黑话(.git/路径、schema 字段、REST 端点等)。覆盖:风格对齐 / Style Alignment
验证 / Verification
pnpm build通过(zh-Hans + en 两个 locale)onBrokenLinks: 'throw'模式下无失效链接pnpm start预览中英文渲染效果关联 / Related
主仓库 PR: https://github.com/desirecore/desirecore/pull/656
内部技术文档:
desirecore-docs#ADR-030 团队仓库管理I have read and agree to the CLA