Skip to content

docs: update community link to discord for zht - #54593

Closed
G36maid wants to merge 1 commit into
anomalyco:devfrom
G36maid:zht-discord-link
Closed

G36maid wants to merge 1 commit into
anomalyco:devfrom
G36maid:zht-discord-link

Conversation

@G36maid

@G36maid G36maid commented Oct 11, 2026 •

Copy link
Copy Markdown
Contributor

Port of #33486 to V2 (dev), re-submitted per maintainer request after the V1 → V2 migration closed all V1 PRs. Original description below (only the issue reference updated, since #27642 was closed as not-planned by the cleanup bot while the fix was pending review).

Issue for this PR

Fixes the problem reported in #27642 (closed as not-planned by the cleanup bot while the fix was pending review).

Type of change

  • Documentation

What does this PR do?

English

Credit: PR #27640 by @changchinlan already solved this cleanly, but it was auto-closed by the stale-PR cleanup (created >1 month ago, <2 positive reactions) — not for any technical reason, and it was never reviewed. This PR revives that contribution.

Background: #16908 routed both the zh and zht locales to a Feishu group. The Traditional Chinese (zht) audience is primarily in Hong Kong, Taiwan, Macau, and overseas communities, where Feishu has very little reach. Practical barriers for that audience joining via Feishu:

  • Feishu signup requires a phone number, and the flow is oriented toward mainland Chinese numbers.
  • Feishu's primary service operates out of mainland China, a consideration for users in jurisdictions with different data-handling expectations.

This PR keeps Feishu for zh (Simplified Chinese) — respecting the intent of #16908 for that audience — and routes zht back to the existing Discord community:

  • packages/console/app/src/component/footer.tsx: narrow the Feishu branch from locale === "zh" || locale === "zht" to locale === "zh".
  • README.zht.md: replace the Feishu link with Discord.
  • packages/console/app/src/i18n/zht.ts: correct the footer.feishu translation from the Simplified 飞书 to the Traditional 飛書. The key is kept (matching en.ts, which also retains it for dictionary completeness) even though the zht locale no longer references it from the footer.

No changes to the zh locale, the en dict, or the /feishu redirect route.

中文

致謝:@changchinlan 先前的 PR #27640 已乾淨地解決此問題,但因閒置被自動清理機制關閉(建立超過 1 個月、正面反應少於 2)—— 並非技術因素,且從未被 review。本 PR 接手該貢獻。

背景:#16908 將 zh 與 zht 兩個語系都導向飛書群組。繁體中文(zht)受眾主要分布於港澳、台灣及海外華人社群,飛書在這些地區普及度極低。透過飛書加入的實際障礙:

  • 飛書註冊需要手機號碼,且流程高度偏向中國大陸號碼。
  • 飛書主要服務由中國大陸營運,對資料處理規範不同的司法管轄區使用者而言是一項考量。

本 PR 保留 zh(簡體中文)的飛書設定(尊重 #16908 對該受眾的用意),並將 zht 重新導回既有的 Discord 社群:

  • packages/console/app/src/component/footer.tsx:將飛書分支從 locale === "zh" || locale === "zht" 縮減為 locale === "zh"。
  • README.zht.md:將飛書連結改為 Discord。
  • packages/console/app/src/i18n/zht.ts:將 footer.feishu 從簡體「飞书」修正為繁體「飛書」。保留此鍵(與 en.ts 一致,後者亦為字典完整性保留它),即便 zht 語系已不再於頁尾引用。

未變更 zh 語系、en 字典或 /feishu 重導路由。

How did you verify your code works?

  • Confirmed language.locale() returns "zht" for Traditional Chinese visitors, which now falls through to the Discord branch in footer.tsx (condition simplified to locale === "zh"; type-equivalent, no new code paths).
  • LSP diagnostics on zht.ts are clean; satisfies Dict still passes because every key remains present (footer.feishu override kept, only corrected to Traditional).
  • footer.discord already exists in zht.ts, so the Discord label renders correctly for zht.
  • Grepped the repo for other footer.feishu references — only the zh and en dicts remain, both intentional.
  • Note: full tsgo --noEmit typecheck could not run in my environment because package dependencies aren't installed; the change is type-equivalent and minimal.

Screenshots / recordings

N/A — link-target and text change only; no visual layout change.

Checklist

  • I have tested my changes locally
  • I have not included unrelated changes in this PR

Added by the opencode bot (AI-generated).

Related: #27642, #16908

The Traditional Chinese (zht) community uses Discord, not Feishu.
The footer previously grouped zht together with zh (Simplified Chinese)
to show the Feishu link, but only Simplified Chinese uses Feishu.

- footer.tsx: restrict the Feishu branch to zh so zht falls through to Discord
- README.zht.md: replace the Feishu link with Discord
- zht.ts: correct footer.feishu from Simplified 飞书 to Traditional 飛書
  (kept for dictionary completeness parity with en.ts, which also retains it)

Co-Authored-By: 張景嵐 <[email protected]>
@github-actions

Copy link
Copy Markdown
Contributor

The following comment was made by an LLM, it may be inaccurate:

@opencode-agent opencode-agent Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

The change looks correct. The footer now sends only zh to Feishu, so zht falls through to the existing Discord entry (footer.discord is already in zht.ts). README.zht.md uses the same Discord link as the other READMEs, and the console app type-checks with the change. I checked it by reading the code and did not render the console page.

Public API: unchanged.

The only open point is not technical: this partly reverts #16908 for Traditional Chinese readers, so maintainers need to agree on which community link zht should get.

Related: #27642, #16908

@github-actions

Copy link
Copy Markdown
Contributor

Automated PR Cleanup

Thank you for contributing to opencode.

Due to the high volume of PRs from users and AI agents, we periodically close older PRs using automated criteria so maintainers can focus review time on the most active and community-supported contributions.

This PR was closed because it matched the following cleanup criteria:

  • The PR was created more than 1 month ago
  • The PR had fewer than 2 positive reactions
  • Positive reactions are counted as thumbs-up, heart, celebration, or rocket reactions on the PR

PRs created within the last month are not affected by this cleanup.

If you believe this PR was closed incorrectly, or if you are still actively working on it, please leave a comment explaining why it should be reopened. A maintainer can review and reopen it if appropriate.

Thanks again for taking the time to contribute.

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant