Skip to content

GitHub achievements: every badge, its tiers and how to earn it

GitHub achievements are small badges in your profile sidebar for specific actions, and seven of them can be earned today. Quickdraw and YOLO depend only on you, Pull Shark can too, and Starstruck, Galaxy Brain and Pair Extraordinaire need other people.

By
GitWow editorial team
Updated
updated
Reading
9 min read

Key takeaways

  • GitHub does not publish tier thresholds, so every number in a badge guide is observed and some of them disagree.
  • Split the badges by who controls them: you alone, other people, or your own decision to sponsor.
  • Retired badges such as Arctic Code Vault stay on the profiles that have them, and cannot be earned now.
  • Showing achievements is a profile setting, and a hidden badge is still visible to you.

Our team has worked on social proof for more than ten years, across accounts that reached over 10 billion people and close to a billion followers. A badge on a developer page is social proof in its smallest form. That is why we sorted GitHub's achievements by the one question that matters before you chase any of them: how much of it is in your hands.

GitHub introduced achievements in 2022, and the list has changed since

Achievements went into public beta on 9 June 2022. They celebrate specific events and actions on GitHub and show up as small badges in the sidebar of your profile. In the launch post GitHub noted that nearly 5,000 public contributions were made every minute in the year before. The first three badges looked different from today's, and two changes followed. In October 2022 you could hide an individual badge, and in September 2026 profiles began showing the highest tier you have earned for a multi-level achievement instead of the first.

Older badges came from other places. The Mars 2020 Contributor badge goes back to the Ingenuity helicopter mission in April 2021, and Arctic Code Vault Contributor to the 2020 code archive. Both are closed now, and the retired section below covers them.

Seven achievements can be earned today, and guides count them differently

BadgeWhat you doTiersEarn it now
Pull SharkGet pull requests mergedYesYes
StarstruckOwn a repository that gets starredYesYes
Pair ExtraordinaireCo-author commits on merged pull requestsYesYes
Galaxy BrainGet your answers accepted in DiscussionsYesYes
QuickdrawClose an issue or a pull request within five minutes of opening itNoYes
YOLOMerge a pull request without a reviewNoYes
Public SponsorSponsor a developer or organization through GitHub SponsorsNoYes
Arctic Code Vault ContributorCode in the 2020 archiveNoClosed
Mars 2020 ContributorCode used by the Ingenuity missionNoClosed
Heart On Your Sleeve, Open SourcererTried by GitHub, then switched offNoDisabled

The count depends on the guide. One tracker lists seven current achievements. Another lists eight by adding Finishing Touch. Older guides say nine because they include the two switched-off badges. Treat seven as the safe number and check your own profile for anything extra.

Tiers need 2, 16, 128 and up, and GitHub publishes none of the numbers

Four achievements have levels: Default, Bronze, Silver and Gold. On the profile the higher ones appear as x2, x3 and x4. GitHub does not publish the thresholds, so the figures below are counts that guides observed on real profiles.

BadgeCountsDefaultBronzeSilverGold
Pull SharkMerged pull requests2161281,024
StarstruckStars on one repository161285124,096
Pair ExtraordinaireMerged pull requests with a co-author1102448
Galaxy BrainAccepted answers281632

Most sources agree on these numbers, and a few do not. One guide gives Pull Shark Bronze at 4 merged pull requests where the others say 16. The same guide puts Galaxy Brain Bronze at 1 accepted answer against 8 elsewhere. Quickdraw has a split too: most sources say you close an issue or a pull request within five minutes, while one says you merge a pull request that fast. Since GitHub is silent, check the live badge on your own profile after you hit a threshold, and trust that over any table. Reading a tier-three badge as proof of volume is safer than reading it as an exact count.

Sort badges by who controls them before you chase any

Guides rank badges by ease, which hides the real question. We group them by what has to happen.

GroupBadgesWhat you need
Only youQuickdraw, YOLO, Pull Shark in your own repositoriesA repository, a few minutes, nobody else
Other peopleStarstruck, Galaxy Brain, Pair ExtraordinaireStars, accepted answers, a co-author
Your own decisionPublic SponsorSponsor someone through GitHub Sponsors

Quickdraw and YOLO, in a repository of your own

  1. Create a throwaway or practice repository you own.
  2. For Quickdraw, open an issue or a pull request and close it within five minutes. If your profile does not show it, repeat once with a merge, since sources differ on which action counts.
  3. For YOLO, open a pull request from a branch and merge it without a review.

Pull Shark, in your repository first

  1. Open two pull requests from branches, one at a time.
  2. Merge both. The status has to read Merged. Closed does not count.
  3. Make sure the commits use an email linked to your account, and that the repositories are public. The same email rule governs the green squares, as the contribution graph guide explains.

Pull requests to other people's public projects count as well, and they give you more than a badge: a merged pull request is real work in a real repository.

The pull request itself can come from four places, and the badge does not care which: the GitHub web editor, your own repository, a contribution to someone else's project, or an IDE or the Git command line, which push the branch you then open as a pull request. What does not count is a pull request that was closed without merging, or one in a repository you cannot see as public. The badge reads state, not effort, so a one-line fix that gets merged beats a large change that is rejected.

Galaxy Brain and Pair Extraordinaire need someone else

For Galaxy Brain, answer questions in the Discussions of public repositories until your answer is marked as accepted. For Pair Extraordinaire, add a Co-authored-by line to a commit in a pull request that gets merged. Both need a second person, so ask a colleague or open-source friend to pair on a small change.

Plan Galaxy Brain around real questions. Search the Discussions tab of a public project you use, pick an unanswered question you can solve and write the answer with the steps. The asker or a maintainer has to mark it as the answer, so a short reply with a working command is more likely to be accepted than a long essay. Pair Extraordinaire is easier to arrange than it looks: when you merge a pull request that you wrote with someone, put the other person in a Co-authored-by line at the bottom of the commit message, using the name and the email linked to their account.

Public Sponsor depends on your own decision to sponsor

The badge goes to people who sponsor a developer or an organization through GitHub Sponsors. It has one level. If you are on the receiving side of sponsorship, the page on how to get GitHub sponsors covers that.

Starstruck needs 16 stars on one repository, and the project has to earn them

Starstruck is the badge that depends most on other people. The first level needs 16 stars on a repository that belongs to your account, then 128, 512 and 4,096. Stars across your whole profile do not add up. They count on a single repository. If you are not sure what a star is, what are GitHub stars answers in a page.

The badge follows the project, so work on the project. A clear README and a stated use make a repository people want to bookmark. We have seen on social accounts that good content lifts anything, and the repository version is a visitor who understands in ten seconds why to star it. The steps for the first 16 are in how to get GitHub stars. One way to start is our free exchange, where members star each other's public repositories by hand from their own accounts, so get free GitHub stars or read about the star exchange.

One more thing to keep apart: the GitHub Stars program, for community ambassadors, shares a name with Starstruck and has nothing to do with it. See that program for the details.

Retired, disabled and Highlights badges are different things

Sources mix these three categories, and the difference decides whether you can still get them.

CategoryExamplesStatus
RetiredArctic Code Vault Contributor, Mars 2020 ContributorNo longer awarded. Those who earned them keep them.
DisabledHeart On Your Sleeve, Open SourcererTried by GitHub and switched off. Some pages call them in testing, others unobtainable.
HighlightsPro, Developer Program Member, GitHub Campus Expert, Security Bug Bounty Hunter, Security Advisory CreditNot achievements. Each marks a program or role, with no tiers.

Arctic Code Vault covers code that went into an archive in 2020, and Mars 2020 covers the Ingenuity helicopter, which has long since landed. Do not spend time looking for a workaround. Highlights are earned by joining a program or taking a role, so they come from outside the contribution flow and are worth a line on a CV only if the program matters to your reader.

Here is what each Highlights badge marks, so you do not look for a way to earn what is really a membership.

  • Pro: the account is on GitHub Pro.
  • Developer Program Member: the account joined the GitHub Developer Program.
  • GitHub Campus Expert: the account holder is part of the Campus Experts program for student communities.
  • Security Bug Bounty Hunter: a valid security report to GitHub's bounty program.
  • Security Advisory Credit: the account is named in a published security advisory.

Show, hide and troubleshoot: the setting comes first

If you cannot see your achievements, check the visibility setting before anything else. Open Settings, Public profile, and look for the Show Achievements on my profile box. Tick it and press Update preferences. To hide one badge, open Achievements in your profile sidebar and use the eye icon on that badge, which GitHub added in October 2022. A hidden badge stays visible to you only.

A new badge usually appears within minutes, and sometimes takes up to a day. If nothing shows after 24 hours, check these in order.

  1. The pull requests are in Merged state, not Closed.
  2. Show Achievements is switched on.
  3. The commit email matches your account.
  4. For Pull Shark, merge one more pull request, which some guides report nudges the badge into place.

Pull requests in private repositories are a separate case. Per GitHub's documentation, your contribution graph and your achievements show activity from public repositories only by default, and you can choose to include private activity. Switch on private contributions if you want your work repositories to count.

The look of some badges depends on a profile setting. Emoji-based achievements follow your Emoji Skin Tone Preference, which you change in the appearance settings.

Show the badges that reflect real work and let the easy ones sit

A badge is a hint, and a reader gives it a few seconds, like the rest of the profile. Quickdraw and YOLO take minutes in a private practice repository, so they tell a visitor nothing about your work and a hiring reader knows it. Pull Shark with tiers, Galaxy Brain and Pair Extraordinaire show you work with other people, which is what a hiring manager wants to hear about. Starstruck shows that strangers found something you built useful. If your profile has room for three badges, keep those and hide the quick ones with the eye icon.

The order we suggest is simple. Earn Pull Shark by contributing to a project you already use. Let Galaxy Brain come from answering questions you would answer anyway. Treat Starstruck as a by-product of a project worth starring. Skip chasing the retired badges, because nobody can get them now.

Track progress with a checker and the profile around the badges

For the overall picture, start with our profile analyzer. It scores twelve checks out of 100 from public data and shows where a badge fits among the other parts of your profile. The achievements themselves are tracked by gh-achievements, a GitHub CLI extension with a web version that lists the badges of any public profile, the tier and how far you are from the next threshold, with no token. Use it before you decide which badge is worth the effort.

Badges sit best on a profile built around them. The sidebar, pins and README are in how to make a good GitHub profile, and when the profile is ready, get free followers so a visitor finds a profile that other developers already follow.

FAQ

Frequently asked questions

Something else? hello@gitwow.org

How many GitHub achievements are there?

Seven can be earned today by one count, eight by another that adds Finishing Touch. Two more are closed for good and two were switched off. Your profile only displays those that are turned on in settings.

What is the easiest GitHub achievement to get?

Quickdraw and YOLO, both done in a repository of your own in a few minutes. Sources disagree on whether Quickdraw means closing or merging within five minutes, so test it and confirm on your profile.

How do I get the Pull Shark badge?

Get two pull requests merged. They must be in Merged state, not Closed. Pull requests in your own or other public repositories count, and your commits need an email linked to your account. Later tiers are reported at 16, 128 and 1,024.

How do I get the Starstruck achievement on GitHub?

You need a repository you own with 16 stars, then 128, 512 and 4,096 for later tiers. The stars count on a single repository, not as a sum across your profile. A clear README helps the repository earn them.

How long does it take for a GitHub achievement to show up?

Usually a few minutes, sometimes up to a day. If nothing changes after 24 hours, check that the pull requests are merged and that Show Achievements is switched on in your public profile settings.

Why can't I see my achievements on my profile?

Most likely the display is off. Go to Settings, Public profile, and tick Show Achievements on my profile. An individual badge can also be hidden with the eye icon, and then only you see it.

Can you still get the Arctic Code Vault or Mars 2020 badge?

No. Both are closed, since the code archive dates from 2020 and the Ingenuity mission is over. People who earned them keep them on their profiles.

Do pull requests in private repositories count?

Only if private contributions are shown. GitHub says the contribution graph and achievements reflect public repositories by default, and you can include private activity in Contribution settings. The same switch changes your green squares.

GitWow is a free community for growing your GitHub repositories and profile with help from other members.

Start free