Skip to content

docs: add missing Chinese language link to Japanese README#327

Merged
Leeaandrob merged 1 commit intosipeed:mainfrom
humaid0x:fix-japanese-readme-link
Feb 17, 2026
Merged

docs: add missing Chinese language link to Japanese README#327
Leeaandrob merged 1 commit intosipeed:mainfrom
humaid0x:fix-japanese-readme-link

Conversation

@humaid0x
Copy link
Contributor

No description provided.

Copy link
Collaborator

@Leeaandrob Leeaandrob left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

PR #327 Deep Review — @humaid0x

Trivial docs fix. The Japanese README was missing the Chinese language link in its navigation header.


Verification

  • Checked out branch locally: fix-japanese-readme-link
  • Verified all 3 README language navigation links are now consistent:
File Navigation
README.md [中文] | [日本語] | English
README.zh.md 中文 | [日本語] | [English]
README.ja.md [中文] | 日本語 | [English]

All three files now form a complete cross-link triangle. No other README language variants exist.


Verdict: APPROVE

1-line fix, zero risk, completes the language navigation. Ready to merge.

@Leeaandrob Leeaandrob merged commit ba47892 into sipeed:main Feb 17, 2026
1 check passed
@Orgmar
Copy link
Contributor

Orgmar commented Feb 19, 2026

@humaid0x Thanks for catching the missing Chinese language link in the Japanese README! Small doc fixes like this make a real difference for discoverability.

We're building the PicoClaw Dev Group on Discord for contributors to connect. If you'd like to join, send an email to support@sipeed.com with the subject [Join PicoClaw Dev Group] + Your GitHub account and we'll send the invite!

SebastianBoehler pushed a commit to SebastianBoehler/picoclaw that referenced this pull request Feb 22, 2026
docs: add missing Chinese language link to Japanese README
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants