i18n(ja): restore literal Expected-Output.txt link text in sample-app guides - #23623
i18n(ja): restore literal Expected-Output.txt link text in sample-app guides#23623yahonda wants to merge 1 commit into
Conversation
|
Warning Review limit reachedNext included review available in 20 minutes. View limit detailsLimit details: You’ve used all 4 included reviews currently available. You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Review configuration: ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (11)
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 |
|
[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 |
What is changed, added or deleted? (Required)
Continuation of the literal-identifier-mistranslation sweep (#23617/#23618/#23619/#23622). 11
develop/dev-guide-sample-application-*.mdfiles link to the actual GitHub fileExpected-Output.txtusing the translated link text期待される出力.txtinstead of the literal filename, e.g.:should be:
All 11 sites verified against the English source (
Check the [Expected-Output.txt](url) to see if the output matches.).Which TiDB version(s) do your changes apply to? (Required)
What is the related PR or file link(s)?
AI agent involvement
Do your changes match any of the following descriptions?