docs: remove root translated readmes#11613
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
| English | <a href="README.zh.md">简体中文</a> | <a href="README.zht.md">繁體中文</a> | <a href="README.ko.md">한국어</a> | <a href="README.de.md">Deutsch</a> | <a href="README.es.md">Español</a> | <a href="README.fr.md">Français</a> | <a href="README.it.md">Italiano</a> | <a href="README.da.md">Dansk</a> | <a href="README.ja.md">日本語</a> | <a href="README.pl.md">Polski</a> | <a href="README.ru.md">Русский</a> | <a href="README.bs.md">Bosanski</a> | <a href="README.ar.md">العربية</a> | <a href="README.no.md">Norsk</a> | <a href="README.br.md">Português (Brasil)</a> | <a href="README.th.md">ไทย</a> | <a href="README.tr.md">Türkçe</a> | <a href="README.uk.md">Українська</a> | <a href="README.bn.md">বাংলা</a> | <a href="README.gr.md">Ελληνικά</a> | <a href="README.vi.md">Tiếng Việt</a> | ||
| </p> | ||
|
|
||
| <p align="center"> |
There was a problem hiding this comment.
WARNING: This removes the only in-repo entry point to the translated READMEs before their replacement paths exist
On the current branch there is no translations/ directory and README.md no longer exposes any non-English docs links. Merging this half of the stack on its own means users on main temporarily lose discoverability of every localized README, and any existing direct links to README.<lang>.md return 404 until the follow-up lands. Consider landing the replacement paths and updated links in the same PR so the docs stay continuously available.
Reply with @kilocode-bot fix it to have Kilo Code address this issue.
Code Review SummaryStatus: 1 Issue Found | Recommendation: Address before merge Overview
Issue Details (click to expand)WARNING
Fix these issues in Kilo Cloud Files Reviewed (22 files)
Reviewed by gpt-5.4-20260305 · Input: 72.3K · Output: 11.8K · Cached: 521.5K Review guidance: REVIEW.md from base branch |
Revert PR #11335 so translated README files no longer live at the repository root.
This is the first half of a stacked change: a follow-up PR will re-add the same translated READMEs under
translations/so future upstream syncs do not see root-file additions followed by Kilo-specific renames.The follow-up can be merged immediately after this PR.