Translate GitHub in Your Browser, Both Ways
To translate GitHub, add a browser extension that translates inline on github.com. Issues, pull request threads, and discussions render in your language in place, and you reply by typing in your own language and translating before you comment, so you collaborate on a project with a foreign-language team without leaving the thread.
Why generic translators break on GitHub
A GitHub thread mixes prose and code, and a naive page translator will happily mangle a code block or a stack trace along with the discussion. Copy-pasting each comment into a separate tab is slow when you are triaging a long issue. Developer collaboration needs the discussion translated while the code stays exactly as written.
Built for GitHub, not bolted on
Swiftin ships bespoke GitHub support, so issue and pull request discussion translates inline while code blocks and inline code are left untouched, keeping snippets and stack traces exactly as written.
Reading GitHub in your language
Read issues, pull request reviews, and discussions in your own language, side-by-side or replacing the original in place, with code blocks left intact so you never lose a snippet to translation.
Writing back in theirs
Reply to an issue or review by typing in your own language and let Input Translation post it in the maintainer language, so you contribute to a foreign-language project without a separate translator.
This writing half is what most translators skip, they only translate what you read, not what you send. It runs across all four core features: page translation, input translation, selection translation, and AI text-to-speech, in 100+ languages.
Setup
- Install Swiftin from the Chrome Web Store
- Sign in (free, no card required)
- Open github.com and use the site as usual
- Click the Swiftin launcher to translate the page in your language
- Type a reply in your own language and trigger Input Translation before sending
