Open-source project
robotze/GithubDesktopZhTool avatar
robotze/GithubDesktopZhTool

GithubDesktopZhTool swaps two JavaScript files into GitHub Desktop, and the version has to match

A Chinese localization tool for GitHub Desktop, supporting Windows, Mac and Linux.

3,907 stars447 forksUnknownLicense varies

At a glance

What is it?
A Chinese localization tool for GitHub Desktop that ships an executable for Windows and raw resource files for macOS and Linux, distributes them through a WeChat account rather than a package manager, and warns that a version mismatch can stop the desktop app opening.
Who is it for?
GithubDesktopZhTool is worth using if you read GitHub Desktop in Chinese, you are on one of the three platforms it covers, and you are willing to treat the tool version as part of your GitHub Desktop upgrade routine. It is not a fit if you need an audited, licensed or reproducible install, because the repository carries no licence, no build files and no test suite, and the archive is fetched from a chat-triggered cloud drive link rather than a release asset.
Can I use it commercially?
Not without permission. GitHub finds no licence file in the repository, and without a licence all rights are reserved by default: you may read the code but not reuse it. Check the README, or ask the authors, before using it.
Is it still maintained?
Yes. The repository last received commits 50 days ago.
What is it written in?
GitHub does not report a main language for this repository.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • robotze/GithubDesktopZhTool3,907 ★ · +100
Star history
Repository2026-09-242026-11-15
robotze/GithubDesktopZhTool3.8k3.9k

100 Stars in the last 52 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

A version mismatch is the one failure the project warns about twice

The README carries a single instruction in bold form and it is a warning, not a feature: keep the GitHub Desktop version matched to the version of this localization tool, otherwise GitHub Desktop may fail to open after you have localized it.

That is the whole safety contract of this project, and it is worth understanding why it exists. The tool does not patch anything at runtime. It overwrites the interface files inside the installed application. If the file you copy in was built for a different release of the desktop app, the mismatch is not detected gracefully, it shows up as an application that will not start.

The second instruction is shorter and more forgiving: if localization fails, just try again. That covers the ordinary case where a copy did not land cleanly. It does not cover the version case, which is why the two notes sit together and only one of them says retry.

Version numbers move quickly here. Three releases are recent, 3.5.8v2 on 2026-05-16, 3.5.12 on 2026-06-02 and 3.6.6 on 2026-09-26, so a user who localized six months ago is several app upgrades behind.

Windows gets an executable, macOS and Linux get two JavaScript files

The three platforms are handled by three different mechanisms, and only one of them is a program you launch.

On Windows the instruction is to open GithubDesktopZhTool.exe and click the localize button. There is a video tutorial linked on a bilibili address for that path, so the tool is a small native wrapper rather than a set of files you place yourself.

On macOS and Linux there is no executable. You copy two files, main.js and renderer.js, from the platform folder in this repository over the ones in your installed GitHub Desktop. That is the entire procedure for both platforms, and it means you are editing an application bundle by hand.

The difference matters for trust and for reversibility. A Windows user runs a program someone else built. A macOS or Linux user edits two files in an application directory and is responsible for putting them back. Neither approach is documented with a checksum, an installer, or an uninstall step.

The macOS and Linux paths end at two hard coded application directories

The macOS resource directory is given as /Applications/GitHub Desktop.app/Contents/Resources/app, and the Linux one as /usr/lib/github-desktop/resources/app. Both are described as the usual location, which is the important word: they are the conventional paths, not verified ones.

Inside those directories you replace main.js and renderer.js with the copies from the Mac folder or the Linux folder in this repository. Those two file names are the Electron convention, the main process and the renderer, which is why this technique works at all: the interface strings live in JavaScript rather than in a compiled binary.

Two practical consequences follow. On Linux, the path under /usr is a system location, so the copy needs elevated rights and any packaging tool that manages GitHub Desktop may overwrite your change on the next update. On macOS, editing the bundle inside a signed application can invalidate the signature, and the README does not say whether that has been handled. Neither point is documented, so both are things to check on your own machine before you rely on the result.

Linux users are pointed at a different GitHub Desktop build

The Linux section does not tell you where to get GitHub Desktop. It points at a separate repository, shiftkey/desktop, as the Linux version of the app.

That is a meaningful difference from the other two platforms. The Windows and macOS instructions assume you already have the official desktop client, and the README opens by linking the official site at desktop.github.com. Linux users are sent to a community distribution instead, which means the file layout you are about to overwrite may not be identical to what the official builds ship, and a mismatch here produces the same failure as a version mismatch: an app that will not open.

So the Linux path has two variables to line up rather than one. You need the app build from shiftkey/desktop to match the localization tool version, and you need its resource directory to be the one named in the instructions. Check both before copying anything over.

The download runs through a WeChat account and a cloud drive link

The release tags exist on GitHub, with the most recent titled GithubDesktop汉化工具 3.6.6, but the README does not tell you to download anything from the release page. The distribution instructions are different: follow the author's WeChat public account, where the account is described as having more detailed documentation and where new versions are announced first, and reply with the code 001 to receive a Baidu Netdisk download address in a follow-up message.

That is the whole install path, and it has consequences for anyone outside mainland China. A chat account, an automatic reply and a cloud drive link are three points where the download can change hands, and none of them gives you a checksum or a signed artifact. The repository itself is thin to match: a compressed archive, the README, and a QR code image for the public account.

The practical advice is to download once, keep the archive, and verify the file names inside it against the platform you need before you run or copy anything. You should also assume that updating means going back through the same channel rather than pulling a new release asset.

Version 3 made the translation come back after an upgrade

The change that matters most for a long term user is described in the v3 notes as automatic persistence of the localization: after you upgrade GitHub Desktop, the Chinese interface returns on its own. Before that, every app upgrade was also a re-localization, because the files you had overwritten were replaced.

Two other v3 items are about coverage. The number of translated entries was described as nearly doubled, and the commit message prompt was adapted to the new Copilot channel, which is the AI assistant inside recent GitHub Desktop releases.

The v2 notes give the history of that last item, since Copilot generating Chinese commit messages was a v2 feature and full customization of the translated content was another. So the project has moved from a fixed string replacement towards something you can adjust, and from a one-off patch towards something that survives an app upgrade. Those are the two axes on which this repository has actually moved, and both matter more than the version number itself.

The detailed notes are pointed at a pinned article in the same public account rather than kept in the repository, so the repository itself records the headlines and not the specifics.

No licence, no build files, and no way to tell what is inside the archive

The repository has three entries: a compressed archive, the README, and the QR code image. There is no source tree, no manifest, no CI configuration, and the declared licence is empty, which means there is no grant of permission attached to the files even though the project is published.

That is the honest state of this repository, and it is a different kind of project from the ones that build their own binaries. There is nothing to audit, no build to reproduce, and no history of how the translated strings were produced. The three platform folders described in the instructions exist inside the archive rather than as visible source.

Maintenance is easy to date. The last push was on 2026-09-26 and the 3.6.6 release was published the same day, so the work is current rather than abandoned. The primary language of the repository is not recorded, and the README is written in Chinese, which means documentation, tutorial videos and release announcements are all in Chinese with no English equivalent in the repository.

Editorial conclusion

GithubDesktopZhTool is worth using if you read GitHub Desktop in Chinese, you are on one of the three platforms it covers, and you are willing to treat the tool version as part of your GitHub Desktop upgrade routine. It is not a fit if you need an audited, licensed or reproducible install, because the repository carries no licence, no build files and no test suite, and the archive is fetched from a chat-triggered cloud drive link rather than a release asset. Before you apply it, confirm the tool version lines up with the GitHub Desktop build you have installed, keep a copy of the original main.js and renderer.js so you can put the app back, and read the tutorial for your platform before overwriting anything.

Frequently asked questions

What does SHA mean when I see it near GithubDesktopZhTool?

Nothing in this project touches Git object hashes. GithubDesktopZhTool replaces the interface files of the GitHub Desktop application, replacing main.js and renderer.js in the app resources, so questions about SHA commit identifiers do not apply to it.

Do I need the GitHub Desktop app before using GithubDesktopZhTool?

On macOS and Linux, yes. The instructions are to copy main.js and renderer.js from the matching platform folder over the ones in an existing install, at /Applications/GitHub Desktop.app/Contents/Resources/app on macOS and /usr/lib/github-desktop/resources/app on Linux. On Windows you run GithubDesktopZhTool.exe instead.

What does GithubDesktopZhTool change about GitHub Desktop?

It changes the display text. Version 3.6.6, published 2026-09-26, was described as nearly doubling the number of translated entries and adapting the commit prompt to the new Copilot channel, and version 3 added persistence so the Chinese interface returns after a GitHub Desktop upgrade.

Where do I get GithubDesktopZhTool, and does it affect my git repository?

It does not change how git stores or hashes anything. The download path runs through the author's WeChat public account, where you reply with 001 to receive a Baidu Netdisk address, and the GitHub release tags exist but are not the documented source. The repository contains one compressed archive, the README and a QR code image.

Official sources

  1. Issues
  2. README
  3. Releases
  4. robotze/GithubDesktopZhTool on GitHub
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/robotze-githubdesktopzhtool.svg)](https://hysenlabs.com/projects/robotze-githubdesktopzhtool)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/robotze-githubdesktopzhtool.svg)](https://hysenlabs.com/projects/robotze-githubdesktopzhtool)

Was this useful?