Pull Shark badge not awarded despite 2 merged PRs into external repositories

[arshbibhaw]

Discussion Type

Question

Discussion Content

Hi,

I have two pull requests merged into repositories I don't own, but the Pull Shark badge hasn't appeared on my profile yet.

Merged PRs:

emmabostian/developer-portfolios#3882 : merged Jul 3, 2026
Evavic44/portfolio-ideas#677 : merged Aug 2, 2026

Both are merged, into different repos, neither of which I own. This should satisfy the requirements for the bronze Pull Shark badge (2 merged PRs).

It's been a few days since the second merge. The badge hasn't shown up under Achievements on my profile (github.com/arshbibhaw).

Is this a known delay, or is something not counting correctly? Happy to provide any additional info.

Thanks

[unseenap]

The Pull Shark achievement is earned when you have at least 2 pull requests merged.
So, based on the two PRs you mentioned, you should meet the requirement for the first Pull Shark achievement, assuming both PRs are correctly associated with your GitHub account.
Sometimes GitHub achievements don't appear on the profile immediately after the requirement is met. There can be a delay while GitHub updates the achievement data, so I would give it a few days and, if necessary, up to a couple of weeks.Even i got my achievement on my profile after few weeks.
If it still doesn't appear after that, I'd recommend checking that:

• Both PRs were actually merged, not just closed.
• You opened the PRs from the GitHub account you're checking.
• The PRs are still publicly accessible and associated with your account.
• Achievements are enabled/visible on your profile.

Since your second PR was merged only recently, I'd wait a little longer before assuming something is wrong. Your two merged PRs should qualify for the first Pull Shark level.

[Codebater]

I looked at your specific case rather than answering generically, and your setup does meet the stated criteria — so this is worth digging into.

What I verified via the REST API just now:

• emmabostian/developer-portfolios#3882: merged: true, author arshbibhaw, base master = the repo's default branch, public, not a fork.
• Evavic44/portfolio-ideas#677: merged: true, author arshbibhaw, base main = default branch, public, not a fork.
• Your profile does render the Achievements section (Starstruck is showing), which rules out the Settings → Public profile → "Show Achievements on my profile" toggle being off — the usual first suspect.

So: two merged PRs, authored by you, into default branches of public non-fork repositories, on an account that displays achievements. The bronze Pull Shark tier (2 merged PRs, then 16/128/1024 for higher tiers) should be satisfied.

On timing, a first-hand data point: awarding is asynchronous — it's processed after the qualifying event, not at merge time. I merged two qualifying PRs on a test account roughly an hour before writing this, and that badge also hasn't appeared yet. Same-day delays are completely normal, and there are plenty of reports of it taking a day or two. Eight days, though, is outside anything I'd call normal processing lag.

What I'd do next, in order:

1. Merge one more qualifying PR. The awarding job runs on qualifying events, and a long-standing pattern in badge threads here is that a "stuck" achievement appears immediately after the next event gives the processor a fresh trigger. This is the cheapest possible test — any merged PR of yours into any public repo's default branch counts, including your own repo.
2. If it still doesn't appear within ~48 h of that, open a ticket at support.github.com with the two PR links. Achievements aren't covered by a public API, so nobody outside GitHub can inspect why the counter didn't increment — but with the criteria demonstrably met, support can look at the account-side state, and delayed-badge tickets do get resolved.

One thing I'd not spend time on: re-checking email settings or contribution-graph rules — achievements key off the PR author account (which the API confirms is you), not off commit email attribution, so that whole family of fixes doesn't apply here.

[harman-2167]

Hi, I'm experiencing the same issue.

GitHub username: harman-2167

I have two pull requests that were opened by me and successfully merged into the default main branch of a public repository:

hiero-hackers/analytics#309
hiero-hackers/analytics#321

Both PRs were merged, and PR #309 was merged about a month ago. However, the Pull Shark achievement still hasn't appeared on my profile.

My Achievements visibility is enabled as well.

Could someone please check why these qualifying PRs aren't being recognized?

[ebndev]

Hi! We appreciate you reaching out to report this issue.

We have provided details about the incident in this discussion.

To keep conversations all in one place and to ensure you receive timely updates, we’ll be closing this post and recommend you comment on or subscribe to the discussion linked above.

We appreciate your patience as we work toward a solution.