How can I earn different GitHub Achievements?

[SoundwaveSys]

Introduce yourself

Hi GitHub Community! 👋

I'm learning GitHub and trying to understand the different GitHub Achievements.

I've already unlocked a couple of achievements, and I'd like to learn more about the others, such as:

• 🦈 Pull Shark
• 🧊 Pair Extraordinaire
• 🚀 Galaxy Brain
• 🌟 Starstruck
• 🤠 Quickdraw
• and other available achievements

Could someone explain what kind of GitHub activities contribute toward these achievements?

I'm especially interested in learning how to earn them through genuine open-source contributions rather than simply creating activities for the badges.

Thanks! 😊

Links (optional)

No response

Where are you in your GitHub journey?

Learning the basics

And where are you going next on GitHub?

I want to start contributing more to open-source projects, work on real issues, create pull requests, and collaborate with other developers while improving my skills.

What technical skills or projects are you working on?

I’m a Computer Engineering student learning Data Structures & Algorithms, Java, web development, Git/GitHub, and AI/ML. I’m currently working on projects like GWEN, an AI assistant/OS, and Ganit Pravinya, an exam management platform. I’m also learning open-source contribution workflows and looking to contribute to beginner-friendly GitHub projects.

Got a question for us? (optional)

What are some good ways for a beginner to start contributing to open-source projects and earn GitHub Achievements through genuine contributions?

[UmeshCode1]

Welcome to the open-source community, @SoundwaveSys! It’s great that you want to earn GitHub Achievements through genuine technical contributions rather than badge-farming. Earning them organically builds real portfolio value and credibility.

Here is a breakdown of how the major achievements work, their tier progression, and practical ways to unlock them through real projects:

---

1. The Core Achievements & Their Triggers

🦈 Pull Shark

• How to earn: Have your pull requests merged into a repository.
• Tiers: Base (2 PRs merged) $\rightarrow$ Bronze / x2 (16 PRs) $\rightarrow$ Silver / x3 (128 PRs) $\rightarrow$ Gold / x4 (1,024 PRs).
• Genuine way to earn:
  • Look for public repositories with label:"good first issue" or help wanted.
  • Academic, library, and tool repositories often need missing unit tests, CI automation (GitHub Actions), or documentation fixes.
  • Note on anti-farming: Merging PRs on your own private/throwaway repos rapidly is often caught by GitHub's rate heuristics; contributing to active third-party public repositories is the most reliable path.

🚀 Galaxy Brain

• How to earn: Have your responses chosen as the Accepted Answer in repositories that use GitHub Discussions with the Q&A category enabled.
• Tiers: Base (2 accepted answers) $\rightarrow$ Bronze (8) $\rightarrow$ Silver (16) $\rightarrow$ Gold / x4 (32 accepted answers).
• Genuine way to earn:
  • Visit active developer ecosystems (e.g., Next.js, Prisma, FastMCP, Supabase, or here in community/community).
  • Answer developers troubleshooting error logs, build issues, or database configurations. When the author or maintainer clicks "Mark as answer", it counts toward Galaxy Brain.

🧊 Pair Extraordinaire

• How to earn: Co-author a commit that gets merged into a default branch via a Pull Request.
• Genuine way to earn:
  • When collaborating with a peer (like on your GWEN or Ganit Pravinya projects), pair-program and add a Git trailer at the end of the commit message:

    git commit -m "Implement authentication middleware
    
    Co-authored-by: CollaboratorName <collaborator@users.noreply.github.com>"
    

  • When that PR is merged, both contributors receive credit and unlock the badge.

🌟 Starstruck

• How to earn: Create a public repository that reaches a stargazers milestone.
• Tiers: Base (16 stars) $\rightarrow$ Bronze (128 stars) $\rightarrow$ Silver (512 stars) $\rightarrow$ Gold (4,096 stars).
• Genuine way to earn:
  • Publish well-documented, reproducible tools, helpful CLI utilities, starter kits, or curated awesome-lists.
  • Share your work on technical platforms (Dev.to, Reddit r/opensource, Hacker News, or LinkedIn) with a clear README, demo GIFs, and installation instructions.

🤠 Quickdraw

• How to earn: Close an issue or pull request within 5 minutes of opening it.
• Genuine way to earn:
  • Usually happens naturally during urgent hotfix releases or when you diagnose and resolve a self-reported issue immediately with a linked commit/PR.

🦝 YOLO

• How to earn: Merge a pull request without code review in a repository where branch protection reviews are optional.

💖 Heart On Your Sleeve / Public Sponsor

• How to earn: Sponsor an open-source developer or maintainer through GitHub Sponsors.

---

2. Crucial Nuances to Keep in Mind

1. Batch Queue Delay: GitHub syncs achievement data asynchronously. Merging a PR or receiving an accepted answer often takes 24 to 48 hours to reflect on your profile badge counters.
2. Profile Settings: Make sure your achievements are public: go to Settings $\rightarrow$ Public profile and ensure "Show Achievements on my profile" is checked.
3. Best Way for Beginners to Start:
   • Search query: is:open is:issue label:"good first issue" no:assignee filtered by your languages of interest (Java, TypeScript, Python).
   • Contributing type definitions, adding automated CI test coverage, or fixing documentation typos are universally appreciated by maintainers and will steadily build your Pull Shark count.

Good luck with your journey and projects! Let the community know if you ever run into specific workflow or Git questions.

[SoundwaveSys]

Thanks for the detailed explanation! I have a couple of questions about the achievements.

I have already had a pull request merged, and I also made a commit with a Co-authored-by trailer with another GitHub user. However, 🦈 Pull Shark and 🧊 Pair Extraordinaire are not showing on my profile yet.

Is there a specific requirement I might be missing, or can achievement updates take some time to appear?

Thanks!

[UmeshCode1]

Great follow-up questions, @SoundwaveSys! Here are the exact reasons why Pull Shark and Pair Extraordinaire haven't appeared yet:

---

1. 🦈 Pull Shark Threshold: It Requires 2 Merged PRs

• The Base tier of Pull Shark does not unlock on your 1st merged PR—it requires at least 2 merged Pull Requests.
• Once your 2nd pull request is merged, you will qualify for the base badge. (The next tiers then scale at 16, 128, and 1,024).

---

2. 🧊 Pair Extraordinaire Trigger Criteria

For Pair Extraordinaire, simply pushing a commit with Co-authored-by to a branch is not enough. The criteria are:

1. Must be merged via a Pull Request: The commit containing the trailer must be merged into the repository's default branch (usually main or master) through a PR. Direct pushes or commits on unmerged branches do not trigger the badge.
2. Trailer Formatting: The git trailer must be separated from the commit subject/body by an empty line, with no leading whitespace:

   Add feature implementation
   
   Co-authored-by: CollaboratorName <collaborator@users.noreply.github.com>
   

3. Verified Email: The email address in <...> must be verified and linked to the collaborator's active GitHub account so GitHub can resolve the user handle.

---

3. Public Repository & Async Batch Processing (24–48h Delay)

• Public Repository Requirement: Achievements are indexed from public repositories. If your PR was merged in a private repo, ensure you have enabled "Include private contributions on my profile" in your contribution settings, though public merges are the most consistent triggers.
• The 24–48h Sync Queue: GitHub computes achievement progression through an asynchronous background reconciliation pipeline. Badge allocations do not update in real-time when the merge button is clicked; it typically takes 24 to 48 hours for the badge to be minted and appear in your profile showcase.

Once your 2nd PR is merged and the batch sweep runs, your badges will light up! Let me know if you run into any formatting edge cases.

[kittimzhe]

@UmeshCode1's breakdown is accurate — one time-sensitive correction to the "24 to 48 hours" note: right now it can take considerably longer, and it's a known issue, not something on your side. On Sep 24 a maintainer confirmed GitHub's internal teams are investigating delays in achievements being awarded and appearing ("In some cases, the delay has lasted several days... We don't currently have a timeline"), with affected users tracked in #203416 — worth subscribing there for the fix announcement.

One more practical note while you're starting out: achievements are re-evaluated against your current activity, so keep the repos that earn your badges public — if they're later deleted or made private, the badge can downgrade or drop off (live example from yesterday: #208902). And double-check what's actually been awarded on the Achievements tab of your profile rather than the sidebar alone.

[malkamanuranga]

Really insightful thread! The tip from @kittimzhe about keeping source repositories public to retain badges over time is something a lot of new contributors overlook.

@SoundwaveSys If you're looking for that 2nd merged PR to hit the base Pull Shark badge, tackling documentation typos or adding basic unit test coverage on repos tagged good first issue is usually the most straightforward path. Looking forward to seeing your progress!