Skip to content

i18n(ja): use katakana for the Git operations commit, push, and fetch in the ai/ti docs - #24147

Open
yahonda wants to merge 1 commit into
pingcap:i18n-ja-release-8.5from
yahonda:fix-ja-ai-ti-git-terms
Open

yahonda wants to merge 1 commit into
pingcap:i18n-ja-release-8.5from
yahonda:fix-ja-ai-ti-git-terms

Conversation

@yahonda

@yahonda yahonda commented Oct 2, 2026 •

Copy link
Copy Markdown
Member

What is changed, added or deleted? (Required)

Uses the common Japanese renderings コミット, プッシュ, and フェッチ for the Git operations commit, push, and fetch in the prose of two ai/ti/ docs. These words had been left in English in Japanese sentences, for example 「必要な変更を commit してください」. Elsewhere in the JA docs, Git operations in prose are written in katakana (for example tidb-cloud/branch-github-integration.md: 「新しいコミットをプッシュする」), and the same file already uses 未コミット and オンデマンドフェッチ.

  • ai/ti/guides/ti-git-workspace-for-agents-example.md: L18, L76, and L93.
  • ai/ti/reference/ti-filesystem-git.md L8. The whole list "status, edit, add, commit, fetch, and push" is rendered as operations: ステータスの確認、編集、追加、コミット、フェッチ、プッシュ.

Commands and identifiers in code (git commit, ti fs commit-layer, --commit-ish, …) are unchanged.

This follows up the review of the 2026-10-01 sync (#24132).

Which TiDB version(s) do your changes apply to? (Required)

Tips for choosing the affected version(s):

By default, CHOOSE MASTER ONLY so your changes will be applied to the next TiDB major or minor releases. If your PR involves a product feature behavior change or a compatibility change, CHOOSE THE AFFECTED RELEASE BRANCH(ES) AND MASTER.

For details, see tips for choosing the affected versions.

  • i18n-ja-release-8.5 (TiDB Japanese documentation for TiDB 8.5 versions)

What is the related PR or file link(s)?

AI agent involvement

  • The changes in this PR were primarily made by an AI agent on behalf of the PR author.

Do your changes match any of the following descriptions?

  • Delete files
  • Change aliases
  • Need modification after applied to another branch
  • Might cause conflicts after applied to another branch

🤖 Generated with Claude Code

Summary by CodeRabbit

  • Documentation
    • Updated Japanese Git guides to use Japanese wording for common Git operations. Instructions and command usage remain unchanged.

… in the ai/ti docs

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@ti-chi-bot

ti-chi-bot Bot commented Oct 2, 2026

Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign lance6716 for approval. For more information see the Code Review Process.
Please ensure that each of them provides their approval before proceeding.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@ti-chi-bot ti-chi-bot Bot added missing-translation-status This PR does not have translation status info. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Oct 2, 2026
@coderabbitai

coderabbitai Bot commented Oct 2, 2026 •

Copy link
Copy Markdown

Review in Change Stack →

Navigate logical layers of code changes, visualize relationships, and explore their blast radius.

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Repository: pingcap/docs/.coderabbit.yaml

Review profile: ASSERTIVE

Plan: Advanced

Run ID: c38e3eb0-dc12-4d69-8ffb-66abf090b84e

📥 Commits

Reviewing files that changed from the base of the PR and between aef06ad and b0df672.

📒 Files selected for processing (2)
  • ai/ti/guides/ti-git-workspace-for-agents-example.md
  • ai/ti/reference/ti-filesystem-git.md

Included review availability: This review used your included allowance. Your plan provides up to 4 included reviews per hour; 2 remain after this review.


📝 Walkthrough

Walkthrough

Two Japanese documents now use Japanese terms for Git operations in explanatory text. The command examples and procedures remain unchanged.

Changes

Japanese Git terminology

Layer / File(s) Summary
Replace English Git terms
ai/ti/guides/ti-git-workspace-for-agents-example.md, ai/ti/reference/ti-filesystem-git.md
The guide and reference replace English Git operation names with Japanese terms in explanatory text. The described commands and procedures do not change.

Priority: ⬇️ Low

Estimated code review effort: 1 (Trivial) | ~3 minutes

Change: Other

Merge Risk: ⚪ Minimal · up to b0df6

This change only translates Git-related explanatory text; commands and instructions remain unchanged, so no actionable merge risk remains.

Architecture Summary

Architecture risk: 🔵 Low · up to b0df6

The change affects 1 system.

Changed systems: ai

Architecture concerns
No architecture-level concerns identified.

Review details

Systems and components

  • observed — ai (service) was modified; 2 changed files map to changed impact.

Before / after behavior

  • observed — Modified behavior in ai/ti/guides/ti-git-workspace-for-agents-example.md: Git 操作名 commit、fetch、push を、それぞれ コミット、フェッチ、プッシュ に変更しました。
  • observed — Modified behavior in ai/ti/guides/ti-git-workspace-for-agents-example.md: 変更を commit するという表記を コミット に変更しました。
  • observed — Modified behavior in ai/ti/guides/ti-git-workspace-for-agents-example.md: 履歴保持に関する説明で、commit と push を コミット と プッシュ に変更しました。
  • observed — Modified behavior in ai/ti/reference/ti-filesystem-git.md: 通常の git コマンドの例を英語表記から日本語表記に変更しました。
🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly and concisely identifies the main change: using katakana for the Git operations commit, push, and fetch in the Japanese AI/TI documentation.
Description check ✅ Passed The description explains the documentation changes, affected files, unchanged code identifiers, target Japanese 8.5 release branch, related PR, AI involvement, and change-category selections. It provi…
Docstring Coverage ✅ Passed 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 ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches 💡 1
🛠️ Fix failing CI checks 💡
  • Commit to this branch
  • Create a new PR
🧪 Generate unit tests (beta)
  • Create a new PR
  • Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Autopilot is currently an internal CodeRabbit preview.


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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

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

Labels

missing-translation-status This PR does not have translation status info. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant