Pull Shark achievement not showing after 2 merged PRs (48+ hours)

[OmairAftab]

🏷️ Discussion Type

Question

💬 Feature/Topic Area

Profile

Body

Hi everyone,

I've had two pull requests merged into a public repository, but the Pull Shark achievement still isn't showing on my profile after 48+ hours.

Details:

Profile: https://github.com/OmairAftab
Repository: https://github.com/pathment/pathment (public)
PR 1 (merged ~2 months ago): [ https://github.com/pathment/pathment/pull/374#event-26953126469 ]
PR 2 (merged ~48+ hours ago): [ https://github.com/pathment/pathment/pull/595#event-29121942368 ]

Both PRs show the purple "Merged" status on their respective pages (not closed-without-merging), and both commits appear correctly in my contribution graph and the repo's contributor insights page. I've checked my profile in both mobile and desktop views — no achievement badges appear under the Highlights section in either.

I've read that achievement recalculation can take some time after merging, so I waited it out before posting, but it's now been well past the typical window I've seen mentioned elsewhere.

Has anyone else run into this, or know if there's a known delay/bug with first-time Pull Shark unlocks specifically? Any pointers appreciated — happy to share more details if useful.

Thanks!

[Mr-Nilarnab]

48+ hours is long enough that I’d start looking beyond the normal profile refresh delay.

Since both PRs are confirmed as merged rather than simply closed, and the contribution graph is already showing the activity, the merge events themselves appear to have been processed correctly. GitHub also treats merge, squash, and rebase as distinct merge methods, so I’d check the actual merge method on both PRs as one of the first things.

I’d also verify that both PRs were actually authored by the same GitHub account that you're checking for the achievement, rather than having commits contributed through another account/email.

If those checks are clean, I'd suspect an achievement-side processing issue rather than a problem with the PRs themselves. At that point, I'd include the two PR numbers, merge timestamps, and screenshots showing the merged state when reporting it, since you've already given enough information to make this reproducible.

Hopefully it’s just the achievement service being slow, but after 48+ hours I think it’s reasonable to treat it as a potential GitHub-side issue rather than simply waiting indefinitely.

[OmairAftab]

Thanks for the detailed checks. here's what I found:

Merge method: Both PRs show as standard merges (not squashed/rebased) — "merged X commit(s) into pathment:staging from OmairAftab:[branch]" — so the merge event correctly ties back to my account.

Commit email: Verified — my commits use omairch035@gmail.com, which is confirmed as a verified email on my GitHub account (github.com/settings/emails).

[OmairAftab]

I contacted github support in this regard and told them all details. i received this message from github support :

"Thank you for reaching out to GitHub Support and for the additional details.

I confirmed that both pull requests were merged into a public repository. Their staging target branch did not prevent eligibility.

I corrected the missing Pull Shark achievement record."

And i got my Pull Shark achievement and now its appearing on my profile

[ebndev]

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

We have provided details about the incident in this discussion.

As your issue has been resolved, I am going to close this discussion however if you continue to experience issues, you can subscribe to the discussion linked above to ensure you receive timely updates.