Repository navigation
Fix duplicated "的" typos in Chinese docs (#21985) - #21987
ti-chi-bot wants to merge 1 commit into
Conversation
Signed-off-by: ti-chi-bot <ti-community-prow-bot@tidb.io>
ti-chi-bot
added
area/develop
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
📝 Walkthrough
Merge Risk: 🟡 Moderate · up to
|
| Check name | Status | Explanation | Resolution |
|---|---|---|---|
| Description check |  |
描述说明了修改范围、示例和无语义变更，但版本选择与 PR 目标不一致。PR 目标为 release-8.5 分支，描述却勾选了 master；同时缺少模板中的相关链接、AI agent involvement 和变更类型检查项。 | 将版本选择改为与目标分支一致的 v8.5，并补充或明确模板中缺失的相关链接、AI agent involvement 和变更类型检查项。 |
-
Check name Status Explanation Title check 标题准确概括了主要变更，即修复中文文档中的重复“的”字错误，并标明了相关 PR。 Docstring Coverage No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0… Linked Issues check Check skipped because no linked issues were found for this pull request. Out of Scope Changes check Check skipped because no linked issues were found for this pull request. Full details: Docstring Coverage
-
Explanation
No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (14 skipped: 14 unsupported.)
-
- Fix all pre-merge checks with AI
✨ Finishing Touches: 💡 1
-
🛠️ Fix failing CI checks: 💡
-
- Commit to this branch
- Create a new PR
🧪 Generate unit tests (beta)
-
- Create a new PR
-
- Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.
Comment @coderabbitai help to get the list of available commands.
|
@ti-chi-bot: The following test failed, say
Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🔇 Additional comments: 13
best-practices/massive-regions-best-practices.md: 1
147-147: LGTM!br/br-use-overview.md: 1
61-61: LGTM!Also applies to: 67-67
develop/dev-guide-build-cluster-in-cloud.md: 1
127-127: LGTM!develop/dev-guide-connection-parameters.md: 1
106-106: LGTM!develop/dev-guide-proxysql-integration.md: 1
131-131: LGTM!develop/dev-guide-use-subqueries.md: 1
91-91: LGTM!releases/release-3.0.0-rc.1.md: 1
25-25: LGTM!sql-plan-management.md: 1
340-340: LGTM!ticdc/ticdc-sink-to-kafka.md: 1
69-69: LGTM!ticdc/ticdc-sink-to-pulsar.md: 1
62-62: LGTM!tidb-lightning/tidb-lightning-logical-import-mode-usage.md: 1
67-67: LGTM!tikv-configuration-file.md: 1
822-822: LGTM!develop/dev-guide-create-secondary-indexes.md-132-132: 1
132-132: 📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win
⚠️ Unverified finding
Verification ran but could not confirm this finding. It is shown for review, not as a verified issue.修改句子，避免不自然的表达。
当前句子中的“对……的解读及算子等不做进一步的展开”和“查看更多关于……”表达不够直接。语言检查也标记了该行。请使用更简洁的句子。
可直接替换的文案
-上方执行计划中的 **TableFullScan**、**IndexRangeScan** 等在 TiDB 内被称为[算子](/explain-overview.md#算子简介)。这里对执行计划的解读及算子等不做进一步的展开，若你对此感兴趣，可前往 [TiDB 执行计划概览](/explain-overview.md)文档查看更多关于执行计划与 TiDB 算子的相关知识。 +上方执行计划中的 **TableFullScan**、**IndexRangeScan** 等在 TiDB 内被称为[算子](/explain-overview.md#算子简介)。这里不再进一步介绍执行计划和算子。如需了解更多信息，请参阅 [TiDB 执行计划概览](/explain-overview.md)文档。依据 Markdown 文档审阅规则：可安全替换连续行时必须提供精确的可提交替换建议。
Sources: Path instructions, Linters/SAST tools
ℹ️ Review info
⚙️ Run configuration
- Configuration used: Repository: pingcap/docs-cn/.coderabbit.yaml
- Review profile: ASSERTIVE
- Plan: Advanced
- Run ID:
a0b544b0-6263-48e2-a6c7-807f20adff6a
📒 Files selected for processing: 14
best-practices/massive-regions-best-practices.mdbr/br-use-overview.mdconfigure-time-zone.mddevelop/dev-guide-build-cluster-in-cloud.mddevelop/dev-guide-connection-parameters.mddevelop/dev-guide-create-secondary-indexes.mddevelop/dev-guide-proxysql-integration.mddevelop/dev-guide-use-subqueries.mdreleases/release-3.0.0-rc.1.mdsql-plan-management.mdticdc/ticdc-sink-to-kafka.mdticdc/ticdc-sink-to-pulsar.mdtidb-lightning/tidb-lightning-logical-import-mode-usage.mdtikv-configuration-file.md
Included review availability: This review used your included allowance. Your plan provides up to 4 included reviews per hour; 3 remain after this review.
| <<<<<<< HEAD | ||
| summary: TiDB 的时区设置由 `time_zone` 系统变量控制，可以在会话级别或全局级别进行设置。`TIMESTAMP` 数据类型的的显示值受时区设置影响，但 `DATETIME`、`DATE` 或 `TIME` 数据类型不受影响。在数据迁移时，需要特别注意主库和从库的时区设置是否一致。 | ||
| ======= | ||
| aliases: ['/docs-cn/dev/configure-time-zone/','/docs-cn/dev/how-to/configure/time-zone/'] | ||
| summary: TiDB 的时区设置由 `time_zone` 系统变量控制，可以在会话级别或全局级别进行设置。`TIMESTAMP` 数据类型的显示值受时区设置影响，但 `DATETIME`、`DATE` 或 `TIME` 数据类型不受影响。在数据迁移时，需要特别注意主库和从库的时区设置是否一致。 | ||
| >>>>>>> 8860d46818 (Fix duplicated "的" typos in Chinese docs (#21985)) |
There was a problem hiding this comment.
🎯 Functional Correctness | 🟠 Major | ⚡ Quick win
先解决未完成的 Git 合并冲突。
当前 front matter 保留了冲突标记，并包含两个不同的 summary。静态站点构建无法可靠解析该 YAML 元数据。请保留修正后的 summary，并合并新增的 aliases。
可直接替换的 front matter
-<<<<<<< HEAD
-summary: TiDB 的时区设置由 `time_zone` 系统变量控制，可以在会话级别或全局级别进行设置。`TIMESTAMP` 数据类型的的显示值受时区设置影响，但 `DATETIME`、`DATE` 或 `TIME` 数据类型不受影响。在数据迁移时，需要特别注意主库和从库的时区设置是否一致。
-=======
aliases: ['/docs-cn/dev/configure-time-zone/','/docs-cn/dev/how-to/configure/time-zone/']
summary: TiDB 的时区设置由 `time_zone` 系统变量控制，可以在会话级别或全局级别进行设置。`TIMESTAMP` 数据类型的显示值受时区设置影响，但 `DATETIME`、`DATE` 或 `TIME` 数据类型不受影响。在数据迁移时，需要特别注意主库和从库的时区设置是否一致。
->>>>>>> 8860d46818 (Fix duplicated "的" typos in Chinese docs (#21985))依据 Markdown 文档审阅规则：可安全替换连续行时必须提供精确的可提交替换建议。
Source: Path instructions
2 participants
This is an automated cherry-pick of #21985
First-time contributors' checklist
What is changed, added, or deleted?
Fix duplicated "的" typos in 15 places across 14 Chinese doc files. Only the duplicated character is removed; no semantic changes.
Examples:
Note:
glossary.mdis intentionally left unchanged because "调度目的的一系列操作" there is a valid "目的" + "的", not a typo.Which TiDB version(s) do your changes apply to?
Summary by CodeRabbit