Pull Shark achievement not appearing after multiple merged pull requests

[UfukNode]

🏷️ Discussion Type

Question

💬 Feature/Topic Area

Profile

Body

Hi,

My Pull Shark achievement is not appearing on my profile even though I have multiple pull requests that were successfully merged.

GitHub username: UfukNode

Merged pull requests:

• docs(base): add mainnet flow to B20 guides chainstack/dev-portal#517
• fix(cli): reject invalid remote prover endpoints 0xMiden/rust-sdk#2376
• fix empty overrides handling in transaction methods ProjectOpenSea/seaport-js#942

I have confirmed that “Show Achievements on my profile” is enabled in my profile settings.

I expected the Pull Shark achievement to appear after meeting the merged pull request requirement, but it still has not appeared.

Could you please help me understand whether this is a profile sync or achievement processing issue?

Thansks.

[edwinsatya]

Hi @UfukNode, this is almost always an eligibility/attribution thing rather than a sync bug, so worth ruling those out before chasing support.

Pull Shark only counts a PR when all of these are true:

• you're the author of the PR (reviewing it, or being listed as co-author, doesn't count)
• the state is Merged, not Closed
• it merged into the repo's default branch

That last one trips up a lot of people. Plenty of projects merge contributions into a dev, staging, or docs branch first and only later bring that into main, and those merges don't register for the badge. Open each of your three PRs and check what the base branch actually was.

Second thing to check is commit attribution. If the commit author email in those PRs isn't one of the verified emails on your account, the PR still shows up in the repo but the contribution isn't tied to you. Quick way to tell: open the Commits tab on the PR — your avatar and username should be linked next to each commit. If it's just a plain name with no avatar, that's your problem.

Third, timing. Achievements are computed asynchronously and 24–48 hours is normal, sometimes longer. If your last qualifying merge was recent, it may simply not have run yet.

If all of that checks out and it's been a few days, two things that have worked for others:

1. Profile → Achievements, hide the Pull Shark badge, then unhide it.
2. Settings → Public profile, turn off "Include private contributions on my profile", save, wait ~5 minutes, turn it back on. That tends to trigger a rebuild of your contribution data.

One caveat worth knowing: Achievements are still a public preview feature and GitHub doesn't award them manually, so support generally can't force a badge onto a profile. The calculation also got tightened over the past year to close off farming, so older tutorials and threshold guides don't always match current behaviour.

If you post back which base branch each of the three PRs merged into, that'd narrow it down fast.

[UfukNode]

Thanks, I checked everything you mentioned.

All three PRs were authored by my account, merged into each repository’s default branch, and the commits are correctly attributed to UfukNode with my GitHub noreply email.

I also tried turning off “Include private contributions on my profile”, saving, waiting several minutes, and turning it back on, but the Pull Shark achievement still did not appear.

The second qualifying PR was merged on August 10, so more than 48 hours have already passed.

Since the usual eligibility and attribution checks all seem correct, is there anything else I can verify, or does this look like an achievement processing issue on GitHub’s side?

[Abdullah-Jalal]

This usually happens for one of two main reasons:

Email mismatch on commits: Make sure the email address associated with the commits/PRs matches a verified email on your UfukNode GitHub account. If the Git config email you used when submitting those PRs isn't linked and verified on your account, GitHub won't attribute the merged PRs to your profile achievements.

Sync / caching delay: Achievements aren't always updated in real-time and can sometimes take 24 to 48 hours to sync across GitHub's servers after a PR is merged.

Since you've already enabled "Show Achievements" in your settings and the PRs are in public non-fork repositories, double-check your commit email settings first. If the email matches and it's been more than 48 hours, it's likely a temporary indexing delay on GitHub's end.

[UfukNode]

Thanks. I checked the commit attribution as well.
All three commits use 208284577+UfukNode@users.noreply.github.com, and GitHub correctly links the author to my UfukNode account.

My second qualifying PR was merged on August 10, so more than 48 hours have already passed.

Since both attribution and timing appear to be fine, this seems more likely to be an achievement indexing/sync issue on GitHub’s side. Is there any other eligibility condition I should check?

[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.