Skip to content

Update README.zh.md - #2006

Open
WuDotNetTech wants to merge 3 commits into
bradygaster:devfrom
WuDotNetTech:patch-1
Open

WuDotNetTech wants to merge 3 commits into
bradygaster:devfrom
WuDotNetTech:patch-1

Conversation

@WuDotNetTech

@WuDotNetTech WuDotNetTech commented Sep 8, 2026

Copy link
Copy Markdown

Add missing translation for chinese

What

Add missing translation for chinese

Why

following translation is missing in chinese version
"Squad is a productivity tool for humans, not a replacement for engineers, reviewers, or decision-makers. People stay accountable for priorities, approvals, and final changes; Squad helps with coordination, repetition, and parallel execution."

How

translate it


⚠️ Quick Check

  • If SDK/CLI source files changed: completed the applicable Changeset step below (npx changeset add / .changeset/*.md, direct CHANGELOG.md entry for maintainers, or skip-changelog label for no user-facing changes)

PR Readiness Checklist

The PR readiness bot will validate these automatically after push.
Check each item before requesting review. See CONTRIBUTING.md for full details.

Branch & Commit

  • Branch created from dev (not main)
  • Branch is up to date with dev (git fetch upstream && git rebase upstream/dev)
  • Verified diff contains only intended changes (git diff --cached --stat)
  • PR is not in draft mode (mark ready when checks pass)
  • Commit history is clean (squash fixups before review)

Build & Test

  • npm run build passes
  • npm test passes (all tests green)
  • npm run lint passes (type check clean)
  • npm run lint:eslint passes
  • For migration PRs (>20 files): include test output summary in PR description

Changeset

  • Changeset added via npx changeset add (if packages/squad-sdk/src/ or packages/squad-cli/src/ changed)
  • Or direct CHANGELOG.md entry (maintainers only — write-protected for external contributors)
  • Or skip-changelog label applied (if no user-facing changes)

Docs

  • README section updated (if new feature/module)
  • Docs feature page (if new user-facing capability)

Exports

  • package.json subpath exports updated (if new module)

Breaking Changes

NO Break Changes

add missing translation
@github-actions

github-actions Bot commented Sep 8, 2026

Copy link
Copy Markdown
Contributor

🟢 Impact Analysis — PR #2006

Risk tier: 🟢 LOW

📊 Summary

Metric Count
Files changed 1
Files added 0
Files modified 1
Files deleted 0
Modules touched 1

🎯 Risk Factors

  • 1 files changed (≤5 → LOW)
  • 1 module(s) touched (≤1 → LOW)

📦 Modules Affected

root (1 file)
  • README.zh.md

This report is generated automatically for every PR. See #733 for details.

@github-actions

github-actions Bot commented Sep 8, 2026

Copy link
Copy Markdown
Contributor

🛫 PR Readiness Check

ℹ️ This comment updates on each push. Last checked: commit 27e9897

PR Scope: 🔧 Infrastructure

⚠️ 3 item(s) to address before review

Status Check Details
Single commit 3 commits — consider squashing before review
Not in draft Ready for review
Branch up to date Up to date with dev
Copilot review No Copilot review yet — it may still be processing
Changeset present No source files changed — changeset not required
Scope clean No .squad/ or docs/proposals/ files
No merge conflicts No merge conflicts
Copilot threads resolved No Copilot review threads
CI passing 6 check(s) still running

Files Changed (1 file, +2 −0)

File +/−
README.zh.md +2 −0

Total: +2 −0


This check runs automatically on every push. Fix any ❌ items and push again.
See CONTRIBUTING.md and PR Requirements for details.

@bradygaster bradygaster left a comment

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewed as PAO (DevRel/i18n). Change is correct in scope: it adds the one paragraph the PR description calls out ("Squad is a productivity tool for humans...") to README.zh.md, in the exact position it appears in README.md (between the "what is Squad" intro paragraph and the "not a chatbot" paragraph). Placement, Markdown formatting, and line-diff size (+2/-0, single file) are all fine. CI is green and the PR is mergeable.

Blocking issue — register/tone inconsistency in the new sentence:

Squad乃面向人类之生产力工具,而非工程师、审阅者或决策者之替代。人们仍须对优先级、审批事宜及最终变更承担责任;Squad则助力协调、重复操作及并行执行。

This uses classical/literary Chinese (文言文) grammar — 乃 (classical copula "is"), 之 (classical possessive particle, used twice), 须 (literary "must") — none of which appear anywhere else in this 300+ line file. The rest of README.zh.md is written in modern vernacular Chinese (是/的/你 constructions throughout, e.g. line 194 "协调员会将消息路由给合适的智能体", line 345 "审阅者锁定"). Dropping a literary-register sentence into an otherwise casual, modern doc reads as a jarring style mismatch to a native reader and doesn't match the project's established voice (the English source is plain modern English, not archaic).

Meaning is accurate and "审阅者" for "reviewer" matches existing usage (line 345), so this is a phrasing/register fix, not a re-translation. Suggested rewrite in the file's existing modern style:

Squad 是面向人类的生产力工具,而不是工程师、审阅者或决策者的替代品。人们仍需对优先级、审批和最终变更负责;Squad 帮助实现协调、重复性工作和并行执行。

Please update the sentence to modern vernacular Chinese consistent with the rest of the document, then this is good to merge.

@WuDotNetTech

WuDotNetTech commented Sep 9, 2026

Copy link
Copy Markdown
Author

Updated, Thanks for the suggestion, Brady! and Squad is fantastic.

@WuDotNetTech

Copy link
Copy Markdown
Author

Reviewed as PAO (DevRel/i18n). Change is correct in scope: it adds the one paragraph the PR description calls out ("Squad is a productivity tool for humans...") to README.zh.md, in the exact position it appears in README.md (between the "what is Squad" intro paragraph and the "not a chatbot" paragraph). Placement, Markdown formatting, and line-diff size (+2/-0, single file) are all fine. CI is green and the PR is mergeable.

Blocking issue — register/tone inconsistency in the new sentence:

Squad乃面向人类之生产力工具,而非工程师、审阅者或决策者之替代。人们仍须对优先级、审批事宜及最终变更承担责任;Squad则助力协调、重复操作及并行执行。

This uses classical/literary Chinese (文言文) grammar — 乃 (classical copula "is"), 之 (classical possessive particle, used twice), 须 (literary "must") — none of which appear anywhere else in this 300+ line file. The rest of README.zh.md is written in modern vernacular Chinese (是/的/你 constructions throughout, e.g. line 194 "协调员会将消息路由给合适的智能体", line 345 "审阅者锁定"). Dropping a literary-register sentence into an otherwise casual, modern doc reads as a jarring style mismatch to a native reader and doesn't match the project's established voice (the English source is plain modern English, not archaic).

Meaning is accurate and "审阅者" for "reviewer" matches existing usage (line 345), so this is a phrasing/register fix, not a re-translation. Suggested rewrite in the file's existing modern style:

Squad 是面向人类的生产力工具,而不是工程师、审阅者或决策者的替代品。人们仍需对优先级、审批和最终变更负责;Squad 帮助实现协调、重复性工作和并行执行。

Please update the sentence to modern vernacular Chinese consistent with the rest of the document, then this is good to merge.

updated

@github-actions

Copy link
Copy Markdown
Contributor

👋 Friendly nudge — this PR has had no activity for 7 days.

What needs attention:

  • 🔄 Changes requested by @bradygaster. Address their feedback and request re-review.
  • ⬇️ 47 commits behind dev. Rebase to pick up latest changes.

If this PR is abandoned, please close it. If it's blocked on something external, leave a comment so the team knows.
This is an automated check that runs on weekdays. It won't nudge the same PR more than once per week.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants