Pull Shark achievement missing after two merged pull requests

[NethmiSamadhi]

🏷️ Discussion Type

Question

💬 Feature/Topic Area

Profile

Body

Hello GitHub Community,

My username is NethmiSamadhi. The Pull Shark achievement has not appeared after two pull requests I authored were merged on October 7, 2026:

NethmiSamadhi/CampusGraph-Core#1
NethmiSamadhi/CampusGraph-Core#2

Both were merged into main in my own public repository. “Show Achievements on my profile” is enabled and saved, and my commit email is verified. More than 24 hours have passed.

Could someone clarify whether these pull requests qualify and suggest how to troubleshoot the missing achievement?

Thank you.

[AnthonyKebadilwe]

How to fix the Pull Shark achievement

Pull Shark is awarded for merged pull requests. The first tier needs 2 merged PRs, and higher tiers unlock at 16, 128 and 1,024. Your two PRs hit the entry mark, so the bar itself isn’t the problem. Work through these steps in order.

1. Check each PR. Open Welcome to GitHub product feedback #1 and Feature Request: Select a column when adding an issue to a project #2 and look for the purple “Merged” badge. A closed PR doesn’t count, and the PR must be authored by your own account, not a bot or a second account.

2. Check the profile setting. Go to Settings, then Public profile, and make sure “Show Achievements on my profile” is ticked. Click “Update profile” at the bottom, because the box does nothing until you save.

3. Look at your profile logged out. Open github.com/NethmiSamadhi?tab=achievements in a private window. Sometimes the badge is there but your cached view is stale. A hard refresh (Ctrl+Shift+R) helps too.

4. Give it a few more days. GitHub awards achievements in batches, and delays of several days are common. Two days isn’t out of the ordinary.

5. Trigger a fresh event. Create a branch, change a line in your README, open a third PR and merge it. A new merge can prompt GitHub to re-check your count, and it puts you past the threshold anyway.

6. Merge a PR in someone else’s repo. I can’t confirm how GitHub treats self-merged PRs, since it doesn’t spell this out in the docs. Plenty of people report earning Pull Shark from their own repos, but others report it never appearing. A typo fix or small docs change on a public project, once the maintainer merges it, removes the doubt.

7. Contact support. If a week passes and nothing changes, open a ticket at support.github.com. Include your username, both PR links and the merge dates, so they can check directly.

Steps 5 and 6 are the ones most likely to get you the badge quickly.