create-or-update-zh-translation-pr

To automate Chinese translation PRs from English docs, use scripts that prepare translation inputs and apply minimal edits to existing Chinese files. This workflow creates or updates target PRs with consistent branches, titles, bodies, and labels.

To synchronize pingcap/docs changes into pingcap/docs-cn, orchestrate repo-local scripts that extract per-file change units from the English source and apply deterministic, minimal edits to the Chinese target files, preserving valid existing translations.

Yes, creating translation PRs for docs-cn requires the gh CLI and jq. You also need a local clone of the docs-cn repository to run the included Python and shell scripts that generate translation-input.json and a ready-to-push translation branch.

The best way to update an existing Chinese translation PR is using a deterministic workflow that re-prepares translation inputs from the English source and applies minimal edits to the target files. This ensures the branch, title, body, and labels remain consistent with upstream rules.

The translation workflow preserves existing valid Chinese translations by applying deterministic, minimal edits to the target files. Scripts prepare per-file change units from the English source and only update the parts that require synchronization.

Automated translation PRs may not match upstream rules if the scripts do not enforce consistent branches, titles, bodies, and labels. This workflow enforces those rules deterministically to align with the gh-util.user.js configuration.