
Every Chinese developer who opens GitHub runs into the same quiet friction. The code is universal, but the furniture around it is not: Pull requests, Issues, Actions, Releases, the settings maze. You can read Python perfectly well and still pause for half a second on a button label. Multiply that pause by a hundred clicks a day and you get a real, if unglamorous, productivity tax.
The community's answer has always been to fix it themselves. For years the standard fix was a userscript: a community-maintained dictionary that swapped English interface strings for Chinese ones as pages loaded. It worked, but it carried the usual userscript baggage — a script manager dependency, a single giant dictionary file, and performance that degraded as GitHub's interface grew more dynamic.
A newer project, published in late October 2026 and quickly picked up by China's developer forum LINUX DO, takes the same idea and rebuilds it as a proper browser extension. It is called GitHub Chinese, it is open source under the MIT license, and it is a good window into how Chinese developers actually solve their own tooling problems: not by waiting for the platform to localize, but by shipping a small, opinionated tool and letting the community argue about the details.
At its core, GitHub Chinese is a Manifest V3 browser extension for Chrome, Edge, Firefox, and Safari. It translates the interface text of github.com, gist.github.com, and githubstatus.com into Simplified or Traditional Chinese. It also works on self-hosted GitHub Enterprise Server sites once you authorize them.
The important design choice is what it does not translate. Your content stays untouched: repository names, READMEs, comments, code, commit messages, and custom labels all remain in their original language. Only the interface chrome — menus, buttons, headings, settings pages — gets swapped. That distinction matters. A tool that rewrote your repository's text would be a liability; a tool that only relabels the furniture is safe to leave running all day.
Translation happens entirely inside the browser. There is no translation API call, no server round-trip, and no page content leaving your machine. The extension ships with two dictionaries of more than 30,000 entries each, organized by page type — repository pages, issues, pull requests, Actions, settings — so the same English word can get the right translation in different contexts. It watches GitHub's React-driven interface and re-translates text as components re-render, so navigating between pages does not require a refresh.
One detail worth noting is how Traditional Chinese is handled. It is not produced by converting Simplified text. The Traditional dictionary is translated from English separately, following the terminology used in Taiwan, Hong Kong, and Macau — so "Fork" becomes "分叉" in Traditional, while Simplified uses "复刻". If you have ever been annoyed by a tool that treats Traditional Chinese as a font swap of Simplified, this is the fix for that annoyance.
The project grew out of frustration with the userscript approach, as its author described in the LINUX DO announcement thread: existing scripts felt slow to match text and bloated, with little room to customize. Building a native extension solved three problems at once.
First, matching is faster and more precise. The extension can hook into page rendering rather than scanning the whole document on a timer, and its dictionary is scoped per page type instead of one flat list.
Second, it can offer a real settings interface. A popup lets you toggle translation on or off for the current page, exclude specific paths (for example, leaving settings pages in English while translating everything else), and add your own dictionary entries that override the built-in ones. Settings can be exported and imported as JSON, which makes it easy to share a team's preferred terminology.
Third, it can do things a userscript cannot do cleanly — which is where the project expands beyond translation into a small GitHub power-tool kit.
Beyond translation, the extension bundles four optional features, most of them off by default:
Download acceleration. For developers in China, fetching large release files from GitHub can be slow. The extension adds mirror options to the usual download spots — the Code dropdown, Raw buttons, release attachments — routed through third-party mirror services, with latency testing and automatic failover to the fastest available mirror. This is opt-in and off by default, and the project's own documentation carries a warning worth repeating: a mirror can see your download URLs and IP address, and could tamper with files, so it should never be used for private repositories or anything sensitive. The extension itself refuses to accelerate private repository pages.
Search filtering. GitHub search is noisy, and the extension ships with a built-in blocklist of 454 accounts known for flooding search results with promotional repositories, plus custom rules by owner, repository, or keyword. Matching results are hidden outright rather than greyed out.
Auto-loading. Paginated lists — issues, pull requests, commits, releases — load the next page automatically as you scroll, with page markers inserted so you can still tell where one page ends and the next begins, up to 30 pages.
Small quality-of-life tweaks. An in-page image viewer, links that open in new tabs, and a "download folder" button that zips an entire directory from a repository page (capped at 1,000 files, 300 directories, and 500 MB).
None of this is revolutionary on its own. The point is the packaging: one extension, installed from a browser store, that fixes the handful of paper cuts Chinese developers hit daily.
GitHub Chinese is not an isolated curiosity. It belongs to a long tradition of Chinese developers building localization and access tooling for platforms that do not localize for them. The same impulse produced the earlier userscripts, the community translation projects for developer documentation, and a whole ecosystem of self-hosted tools — from server panels like 1Panel to unified cloud-drive front ends like OpenList — that make foreign platforms feel local.
That tradition also explains the project's reception. Within days of its announcement, the LINUX DO thread drew dozens of replies and thousands of views, and the repository gathered several hundred stars. Forum users debated terminology choices, reported untranslated strings, and asked for features — the usual lifecycle of a community tool finding its audience. The author had already been iterating in public, with a build log thread documenting the extension's development before release.
If you read Chinese and use GitHub daily, the case is straightforward: install it from your browser's extension store, leave the translation on, and leave the acceleration and filtering features off until you want them. The translation layer is local, reversible, and per-page excludable, so the risk of trying it is close to zero.
If you do not read Chinese, the project is still worth a look for a different reason. It is a clean example of a localization architecture done right: dictionary-based rather than machine-translated, scoped by page type, respectful of user content, and honest about the trade-offs of its network features. Any team building a browser extension that modifies a third-party site could learn from its restraint — translate the chrome, never the content, and say plainly what your mirrors can see.
GitHub may one day ship an official Chinese interface. Until then, its Chinese-speaking users will keep doing what they have always done: building the missing piece themselves, and sharing it for free.
Sources: the project's repository at github.com/setube/github-chinese, and the announcement discussion on LINUX DO.