Your GitHub Profile Is Hiding Achievements You Didn't Know Existed
You've probably seen those little badges on someone's GitHub profile—the ones that look like game achievements—and wondered how they got them. Maybe you assumed they required years of open-source contributions or some insider access. The truth is, most of them are earned through specific, often quirky actions that GitHub never clearly documents. That's where the Get-Github-Achievements repository comes in—it's a community-driven guide that spells out exactly what each badge is and how to unlock it.
What It Does
This project is essentially a reference manual for GitHub's achievement system. It catalogs every publicly known badge, from the widely-seen Pull Shark (which you get for having pull requests merged) to the more obscure ones like Galaxy Brainster or Starstruck. For each achievement, the README explains the exact requirements and any notes about edge cases—like whether private repositories count or if there's a time limit.
The repository is structured as a single comprehensive README, but here's the clever part: it's fully translated into over a dozen languages. You'll find versions in English, Persian, Arabic, German, French, Russian, Turkish, Dutch, Chinese, Spanish, Indonesian, Hindi, Japanese, Armenian, Swahili, and Portuguese. The maintainers clearly wanted this to be accessible to developers worldwide, not just the English-speaking majority. It's a simple format—no fancy docs site, no elaborate tooling—just a well-organized list that gets straight to the point.
Why It's Cool
What makes this project genuinely useful isn't the badge list itself—you could probably find that scattered across blog posts and forum threads. It's the consolidation and the attention to detail.
-
The requirements are precise, not vague. GitHub's own documentation on achievements is famously thin. This repo fills in the gaps with specifics. For example, it doesn't just say "get a pull request merged"—it clarifies the nuances that GitHub leaves ambiguous, like whether forks count or if there's a minimum age for your account.
-
It's community-maintained and updated. GitHub occasionally adds new achievements or changes the rules for existing ones. A static blog post from 2022 is going to be outdated. This repository benefits from ongoing contributions, so when GitHub tweaks something, the guide gets corrected.
-
The multilingual approach is a real differentiator. Most developer tools assume you read English. This project actively removes that barrier by offering the full guide in 16+ languages. That's a meaningful choice for a global developer community, and it's rare to see a README put that much effort into localization.
-
It treats achievements like a game. The badge system is gamification by design. This repo leans into that by framing each achievement as a challenge with clear objectives. If you're the type of person who likes completing collections or optimizing your profile, this gives you a checklist to work through.
-
It's honest about limitations. The README includes notes about known issues and quirks, like achievements that don't trigger immediately or ones that have been retired. It doesn't promise you'll get every badge—it just tells you what the conditions are and lets you decide if it's worth pursuing.
How to Try It
Getting started is as simple as opening the repository. There's no installation, no CLI tool, no code to run.
- Head to the repository page.
- Browse the English README, or click the language badge at the top for your preferred translation.
- Scan the table of achievements. Each entry shows the badge name, its icon, and the requirements to earn it.
- Pick one you're close to earning—maybe you already have a few merged PRs or a repository that's gaining stars—and check the specific conditions.
- If you notice an achievement is missing or the requirements have changed, you can contribute by opening an issue or submitting a pull request.
The project doesn't have a website or a package to install. It's a living document, and that's exactly what makes it work. Bookmark it, check back occasionally, and see if there's a new badge to chase.
Final Thoughts
This repository is best for developers who care about their GitHub presence—whether you're job hunting and want a polished profile, or you just enjoy the gamified side of open source. It's not going to make you a better programmer, and it's not a hack to fake contributions. What it does well is demystify a system that GitHub itself keeps opaque. The honest, community-driven approach means you're getting information that's been vetted by people who actually earned the badges, not speculation. If you've ever looked at someone's profile and wondered how they got that one cool badge, this is your answer key. And if you're new to open source, it might just give you a few concrete goals to aim for—which isn't a bad way to start contributing.
Follow @githubprojects for more developer tools and open source projects.