What is github-achievements-hunter?

GitHub profile pages can display small achievement badges that you earn by completing specific actions on the platform, such as getting your pull requests merged, co-authoring commits with another developer, or having many people star one of your repositories. These badges are cosmetic, but they are visible on your public profile and some developers enjoy collecting them. This repository is a guide and toolkit aimed at helping people unlock all of them. The README lists all 22 known GitHub achievements with the conditions required to earn each one. Some are one-time unlocks, such as merging a pull request without requesting a code review (the Yolo badge) or closing an issue within five minutes of opening it (the Quickdraw badge). Others have multiple tiers that scale with how often you repeat the action, such as the Pull Shark badge, which upgrades from bronze to gold as you accumulate more merged pull requests over time. The repository includes a set of shell scripts intended to automate the easiest achievements. A master script called unlock-all.sh runs the others in sequence. Individual scripts handle specific badges: quickdraw.sh opens and immediately closes a GitHub issue to trigger the Quickdraw badge, and yolo.sh helps with the self-merge scenario. The project is designed to run inside GitHub Codespaces, which is GitHub's browser-based development environment, so you do not need to install anything locally. Not all achievements can be automated. Some depend on other people's actions, like earning a certain number of stars on a repository or having other users accept your answers in GitHub Discussions. The README groups these into a phased roadmap: easy automated wins on day one, community-dependent actions over a week, and longer-term goals like building a popular repository over a month. The project is primarily a reference guide paired with utility scripts. The README is a reasonable starting point for anyone who wants to understand what GitHub achievements exist and which ones require genuine community engagement versus ones that can be triggered quickly.