feat(website): Add Turkish (Türkçe) language support#1194
Conversation
|
Important Review skippedAuto incremental reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
📝 WalkthroughWalkthroughThis PR introduces comprehensive Turkish localization for the Repomix documentation site, including VitePress configuration updates to register the Turkish locale and a complete set of Turkish guide documentation pages covering installation, usage, features, configuration, development, and community resources. Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~25 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
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 |
Summary of ChangesHello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! このプルリクエストは、Repomixのドキュメントウェブサイトにトルコ語 (Türkçe) のサポートを追加することで、国際的なユーザーベースへのリーチを拡大することを目的としています。Google Analyticsのデータ分析に基づき、高いエンゲージメント率と中程度の英語力を持つトルコ語ユーザーへのローカライズが効果的であると判断されました。これにより、より多くの開発者が母国語でRepomixの情報を利用できるようになり、ユーザーエクスペリエンスが向上します。 Highlights
🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console. Changelog
Activity
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #1194 +/- ##
=======================================
Coverage 87.14% 87.14%
=======================================
Files 115 115
Lines 4310 4310
Branches 998 998
=======================================
Hits 3756 3756
Misses 554 554 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Add Turkish localization to the repomix.com documentation website. Translated all 25 pages from English, including the VitePress config (nav, sidebar, search UI) and full guide content. Turkish was identified as the next best language to add based on: - Google Analytics data showing Turkish users with high engagement rate (61%) - Cursor docs supporting Turkish among its 12 languages - Medium English proficiency among Turkish developers (higher localization ROI)
yamadashy
force-pushed
the
feat/add-turkish-translation
branch
from
9cf245f to
d09626c
Compare
Deploying repomix with
|
| Latest commit: |
86d8008
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://61dc1597.repomix.pages.dev |
| Branch Preview URL: | https://feat-add-turkish-translation.repomix.pages.dev |
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
このプルリクエストは、ウェブサイトにトルコ語のサポートを追加するもので、素晴らしい貢献です。Google Analyticsのデータに基づいた言語選択の判断も合理的です。
コードの変更点を確認したところ、いくつかの軽微な修正点を提案しました。
config.tsファイルのインポート順序を整理し、メンテナンス性を向上させる提案。- いくつかのマークダウンファイルで、VitePressのカスタムコンテナ構文のタイポ (
::::->:::) を修正する提案。
これらの修正により、コードの一貫性とドキュメントの表示が改善されます。全体として、よく準備されたプルリクエストだと思います。
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 5
🧹 Nitpick comments (6)
website/client/src/tr/index.md (2)
53-56: Optional: Consider adding language identifier to fenced code block.The fenced code block contains a natural language prompt example. While adding a language identifier isn't strictly necessary for non-code content, you could consider using
textormarkdownfor consistency.📝 Optional: Add language identifier
-``` +```text Bu dosya, depodaki tüm dosyaları tek bir araya getirir. Kodu yeniden yapılandırmak istiyorum, önce lütfen gözden geçirin.</details> <details> <summary>🤖 Prompt for AI Agents</summary>Verify each finding against the current code and only fix it if needed.
In
@website/client/src/tr/index.mdaround lines 53 - 56, The fenced code block
that currently contains the Turkish prompt text ("Bu dosya, depodaki tüm
dosyaları tek bir araya getirir. Kodu yeniden yapılandırmak istiyorum, önce
lütfen gözden geçirin.") should include a language identifier (e.g., text or
markdown) on the opening fence; update the fenced block so it begins with
text (ormarkdown) to make the block language-explicit and consistent with
other examples in tr/index.md.</details> --- `242-242`: **Optional: Turkish grammar suggestion.** The static analysis tool suggests that the question particle should be written together: "yardımamı" instead of "yardıma mı". However, this is a very minor stylistic point and both forms are commonly used in Turkish. <details> <summary>📝 Optional grammar adjustment (if preferred)</summary> ```diff -::: tip Daha fazla yardıma mı ihtiyacınız var? 💡 +::: tip Daha fazla yardımamı ihtiyacınız var? 💡 ``` Note: This is purely optional as both forms are acceptable in Turkish. </details> <details> <summary>🤖 Prompt for AI Agents</summary> ``` Verify each finding against the current code and only fix it if needed. In `@website/client/src/tr/index.md` at line 242, Replace the tip string "Daha fazla yardıma mı ihtiyacınız var? 💡" in tr/index.md with the suggested wording "Daha fazla yardımamı ihtiyacınız var? 💡" (update the literal inside the tip block starting with "::: tip") so the question particle is written together as requested. ``` </details> </blockquote></details> <details> <summary>website/client/src/tr/guide/use-cases.md (1)</summary><blockquote> `62-150`: **Optional: Add language identifiers to prompt example code blocks.** Multiple fenced code blocks containing AI prompt examples (lines 62, 69, 76, 83, 90, 97, 104, 113, 120, 127, 136, 143, 150) don't have language identifiers. While these are natural language prompts rather than code, adding `text` as the language identifier would follow markdown best practices and may improve rendering in some contexts. <details> <summary>📝 Optional: Add language identifiers</summary> Example for line 62: ```diff -``` +```text Bu kod tabanında sunucuda bir bellek sızıntısı sorunu var. Uygulama birkaç saat çalıştıktan sonra çöküyor. Lütfen tüm kod tabanını analiz edin ve olası nedenleri belirleyin. ``` ``` Apply the same pattern to all other prompt examples throughout the file. </details> <details> <summary>🤖 Prompt for AI Agents</summary>Verify each finding against the current code and only fix it if needed.
In
@website/client/src/tr/guide/use-cases.mdaround lines 62 - 150, Summary:
Several fenced prompt examples in use-cases.md lack language identifiers; add
"text" to each fenced code block to follow markdown best practices. Fix: locate
each fenced block containing the Turkish prompt strings (e.g., "Bu kod tabanında
sunucuda bir bellek sızıntısı sorunu var..." and the other prompt examples shown
at lines 62, 69, 76, 83, 90, 97, 104, 113, 120, 127, 136, 143, 150) and change
the opening fences fromtotext so they becometext ...; ensure
every example block in the file (all prompt examples) is updated consistently.</details> </blockquote></details> <details> <summary>website/client/src/tr/guide/development/index.md (1)</summary><blockquote> `55-70`: **Add language specifier to project structure code block.** The project structure code block lacks a language identifier. <details> <summary>Proposed fix</summary> ```diff -``` +```text src/ ├── cli/ # CLI implementation ``` </details> <details> <summary>🤖 Prompt for AI Agents</summary>Verify each finding against the current code and only fix it if needed.
In
@website/client/src/tr/guide/development/index.mdaround lines 55 - 70, Add a
language specifier to the project structure code block in the markdown file
(index.md) so the block shows as plain text; locate the fenced code block that
begins withand the tree listing under the guide/development content and change the opening fence to include `text` (i.e.,text) to ensure proper
formatting and syntax highlighting.</details> </blockquote></details> <details> <summary>website/client/src/tr/guide/prompt-examples.md (1)</summary><blockquote> `6-14`: **Consider adding language specifier to fenced code blocks.** The prompt example code blocks lack language specifiers. Since these contain natural language text rather than code, consider using `text` as the language identifier for consistency with markdownlint rules. <details> <summary>Example fix for the first block</summary> ```diff -``` +```text Bu kod tabanının mimarisini analiz et: ``` </details> This applies to all prompt blocks throughout the file (lines 6, 17, 28, 41, 50, 60, 72, 83, 92). <details> <summary>🤖 Prompt for AI Agents</summary>Verify each finding against the current code and only fix it if needed.
In
@website/client/src/tr/guide/prompt-examples.mdaround lines 6 - 14, All
fenced code blocks in prompt-examples.md are missing a language specifier;
update each triple-backtick block (e.g., the block starting with "Bu kod
tabanının mimarisini analiz et:" and the other prompt examples) to use the
"text" language identifier (changetotext) so markdownlint and renderers
treat them as plain text consistently.</details> </blockquote></details> <details> <summary>website/client/src/tr/guide/configuration.md (1)</summary><blockquote> `296-304`: **Add language specification to code fence.** The code block should specify a language for syntax highlighting and better accessibility. <details> <summary>📝 Proposed fix to add language specification</summary> ```diff -**Dizin Yapısı Çıktısı:** -``` -src/ - index.ts - utils.ts -assets/ - logo.png -build/ - app.jar -``` +**Dizin Yapısı Çıktısı:** +```text +src/ + index.ts + utils.ts +assets/ + logo.png +build/ + app.jar +``` ``` </details> As per coding guidelines, markdownlint flagged this as MD040 (fenced-code-language). <details> <summary>🤖 Prompt for AI Agents</summary>Verify each finding against the current code and only fix it if needed.
In
@website/client/src/tr/guide/configuration.mdaround lines 296 - 304, The
fenced code block in configuration.md lacks a language tag (causing MD040);
update the block around the directory listing (the triple-backtick block showing
src/, assets/, build/) to include a language specifier (e.g., use ```text) and
add the optional preceding caption "Dizin Yapısı Çıktısı:" as shown in the
proposed fix so the block becomes a labeled, language-specified fenced block;
edit the code fence in the same snippet (the directory listing block) to add the
language token.</details> </blockquote></details> </blockquote></details> <details> <summary>🤖 Prompt for all review comments with AI agents</summary>Verify each finding against the current code and only fix it if needed.
Inline comments:
In@website/client/src/tr/guide/configuration.md:
- Line 252: The link fragment '#binary-files-handling' is incorrect and should
match the Turkish heading "İkili Dosya İşleme"; update the link in the sentence
that currently uses '#binary-files-handling' to the heading's slug (use
'#ikili-dosya-isleme') so the internal anchor matches the "İkili Dosya İşleme"
section and resolves MD051.In
@website/client/src/tr/guide/index.md:
- Around line 30-33: Add a language identifier to the fenced code block so the
markdown linter rule MD040 is satisfied and rendered output is clearer; update
the triple-backtick fence surrounding the Turkish text in the guide (the fenced
block that starts with "Bu dosya, depodaki tüm dosyaları tek bir araya
getirir.") to include a language tag such as text (e.g., ```text) at the opening
fence.In
@website/client/src/tr/guide/repomix-explorer-skill.md:
- Line 19: The heading "Uzak depoları analiz etme" is currently an h4 (####)
directly under an h2 and should be h3 to preserve proper hierarchy; update that
heading markup from #### to ### and likewise change the similar misplaced
heading at line 26 to ### so the document outline flows h2 → h3 → h4 as
intended.In
@website/client/src/tr/guide/usage.md:
- Line 223: The link text "Ayrıntılı seçenekler için Yapılandırma
Rehberi'ne bakın." points to a hardcoded root path and
always routes to the default locale; update the link target in
website/client/src/tr/guide/usage.md so it uses a locale-aware URL (e.g.,
replace "/guide/configuration" with a locale-prefixed path or the project's i18n
helper/localePath for the configuration guide) so the Turkish docs are opened
when viewing the Turkish site.- Around line 148-158: The fenced code block showing the "Token Count Tree" in
website/client/src/tr/guide/usage.md lacks a language tag (triggering MD040);
update that fenced block to include a language identifier (e.g., "text") after
the opening backticks so the block becomestext ..., preserving the
existing block content and formatting; locate the token tree block in usage.md
(the block containing "🔢 Token Count Tree:" and the ASCII tree) and add the
language identifier to the opening fence.
Nitpick comments:
In@website/client/src/tr/guide/configuration.md:
- Around line 296-304: The fenced code block in configuration.md lacks a
language tag (causing MD040); update the block around the directory listing (the
triple-backtick block showing src/, assets/, build/) to include a language
specifier (e.g., use ```text) and add the optional preceding caption "Dizin
Yapısı Çıktısı:" as shown in the proposed fix so the block becomes a labeled,
language-specified fenced block; edit the code fence in the same snippet (the
directory listing block) to add the language token.In
@website/client/src/tr/guide/development/index.md:
- Around line 55-70: Add a language specifier to the project structure code
block in the markdown file (index.md) so the block shows as plain text; locate
the fenced code block that begins with ``` and the tree listing under the
guide/development content and change the opening fence to includetext(i.e.,In `@website/client/src/tr/guide/prompt-examples.md`: - Around line 6-14: All fenced code blocks in prompt-examples.md are missing a language specifier; update each triple-backtick block (e.g., the block starting with "Bu kod tabanının mimarisini analiz et:" and the other prompt examples) to use the "text" language identifier (change ``` to ```text) so markdownlint and renderers treat them as plain text consistently. In `@website/client/src/tr/guide/use-cases.md`: - Around line 62-150: Summary: Several fenced prompt examples in use-cases.md lack language identifiers; add "text" to each fenced code block to follow markdown best practices. Fix: locate each fenced block containing the Turkish prompt strings (e.g., "Bu kod tabanında sunucuda bir bellek sızıntısı sorunu var..." and the other prompt examples shown at lines 62, 69, 76, 83, 90, 97, 104, 113, 120, 127, 136, 143, 150) and change the opening fences from ``` to ```text so they become ```text ... ```; ensure every example block in the file (all prompt examples) is updated consistently. In `@website/client/src/tr/index.md`: - Around line 53-56: The fenced code block that currently contains the Turkish prompt text ("Bu dosya, depodaki tüm dosyaları tek bir araya getirir. Kodu yeniden yapılandırmak istiyorum, önce lütfen gözden geçirin.") should include a language identifier (e.g., text or markdown) on the opening fence; update the fenced block so it begins with ```text (or ```markdown) to make the block language-explicit and consistent with other examples in tr/index.md. - Line 242: Replace the tip string "Daha fazla yardıma mı ihtiyacınız var? 💡" in tr/index.md with the suggested wording "Daha fazla yardımamı ihtiyacınız var? 💡" (update the literal inside the tip block starting with "::: tip") so the question particle is written together as requested.
ℹ️ Review info
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (28)
website/client/.vitepress/config.tswebsite/client/.vitepress/config/configShard.tswebsite/client/.vitepress/config/configTr.tswebsite/client/src/tr/guide/agent-skills-generation.mdwebsite/client/src/tr/guide/claude-code-plugins.mdwebsite/client/src/tr/guide/code-compress.mdwebsite/client/src/tr/guide/command-line-options.mdwebsite/client/src/tr/guide/comment-removal.mdwebsite/client/src/tr/guide/community-projects.mdwebsite/client/src/tr/guide/configuration.mdwebsite/client/src/tr/guide/custom-instructions.mdwebsite/client/src/tr/guide/development/index.mdwebsite/client/src/tr/guide/development/using-repomix-as-a-library.mdwebsite/client/src/tr/guide/github-actions.mdwebsite/client/src/tr/guide/index.mdwebsite/client/src/tr/guide/installation.mdwebsite/client/src/tr/guide/mcp-server.mdwebsite/client/src/tr/guide/output.mdwebsite/client/src/tr/guide/privacy.mdwebsite/client/src/tr/guide/prompt-examples.mdwebsite/client/src/tr/guide/remote-repository-processing.mdwebsite/client/src/tr/guide/repomix-explorer-skill.mdwebsite/client/src/tr/guide/security.mdwebsite/client/src/tr/guide/sponsors.mdwebsite/client/src/tr/guide/tips/best-practices.mdwebsite/client/src/tr/guide/usage.mdwebsite/client/src/tr/guide/use-cases.mdwebsite/client/src/tr/index.md
…issues - Fix 22 internal links missing /tr/ prefix across 6 files - Add language specifier to fenced code blocks (MD040) - Fix heading level hierarchy in repomix-explorer-skill.md - Fix broken anchor link in configuration.md
PR Review: feat(website): Add Turkish (Türkçe) language supportSummaryThis PR adds comprehensive Turkish localization to the Repomix documentation website. It introduces 25 translated Markdown files, a new VitePress locale config ( Overall AssessmentThe PR is well-structured and ready to merge. The translation is comprehensive, the config structure is fully consistent with existing locales, and the integration follows established patterns. Detailed Findings✅ Configuration consistency (no issues)
✅ Content completeness (no issues)
ℹ️ English code comments in examples (consistent with other locales)The code examples in ℹ️ Minor observation: typo in index.md line 55In
This appears to be a minor typo — "herkesiz" looks like it should be "herkes" ("everyone") or "herkesiniz" depending on the intended meaning. The sentence seems to aim for "This wouldn't be possible without everyone who uses and supports Repomix" — a native Turkish speaker should confirm the correct phrasing. Security & Performance
Pre-mortem Analysis
VerdictApprove — Clean, well-structured translation that follows all existing patterns. The only minor item is the possible typo in 🤖 Generated with Claude Code |
Responses to Bot Review Comments
CodeRabbitAI Inline Comments1.
The anchor 2.
The code block already uses the 3.
The heading at line 19 is 4.
The link already correctly uses the Turkish locale prefix: 5.
The code block already uses the Gemini Code Assist Inline CommentsImport order in
The imports are already in alphabetical order (De, EnUs, Es, Fr, Hi, Id, It, Ja, Ko, PtBr, Ru, Shard, Tr, Vi, ZhCn, ZhTw). No reordering needed. VitePress container syntax (
No instances of Devin AI IntegrationThe Devin review mentioned 1 potential issue as an inline comment. Unable to access the specific inline comment content due to API restrictions, but the PR files have been verified for common issues. |
1 participant
Added Turkish (Türkçe) support to repomix.com's documentation website.
Based on an analysis of Google Analytics data, Turkish was determined to be the optimal language to add next:
Changes
website/client/.vitepress/config/configTr.tswith nav, sidebar, and search UI translationsconfig.tsto registertrlocale (Türkçe)configShard.tsto include Turkish search translationswebsite/client/src/tr/Checklist
npm run testnpm run lint