Missing "Pull Shark" achievement badge after multiple merged PRs

[Xxcool]

🏷️ Discussion Type

Question

💬 Feature/Topic Area

Profile

Body

Hi GitHub Community,

I am experiencing the same issue mentioned in a closed discussion (#169228). I have successfully merged multiple Pull Requests into public repositories (for example, juejin-cn/juejin-usage PR #54, #56 and #76).

Importantly, these PRs were merged over a week ago (early September), so this is definitely not a standard 24-48 hour sync delay.

My "Show Achievements on my profile" setting is turned on, and my commit email strictly matches my verified GitHub email.

However, the "Pull Shark" badge is still completely missing from my profile.

Since the official support ticket redirected me to the community, could a team member please help investigate and trigger a manual sync for my account achievements?

Thank you!

[ArulOly]

Hi,

If the PRs have already been merged for more than a week and the account settings and verified email are correct, this sounds like it may be an achievement-association issue rather than the normal 24–48 hour delay.

The Pull Shark achievement is based on qualifying merged pull requests, so I would first verify that the PRs were actually merged (rather than closed), that they were merged into the repository's default branch, and that the GitHub account is the author/participant associated with those PRs.

If all of those conditions are satisfied, there doesn't appear to be a user-accessible way to manually force an achievements re-sync. Since GitHub Support has redirected you to the Community, I would include the exact PR URLs, merge dates, your username, and screenshots of the enabled achievement setting in the discussion and ask a GitHub Community moderator/staff member to escalate it for investigation.

I would avoid opening/closing or modifying PRs just to try to trigger the badge. If the PRs already qualify, the issue is more likely with GitHub's backend achievement processing than with your repository activity.

[Xxcool]

Thanks for the reply! Here are the exact PR links for reference:

• feat(web): add cascaded model filter juejin-cn/juejin-usage#54
• fix(desktop): add manual retry for failed update restart juejin-cn/juejin-usage#56
• fix(desktop): compile auto-update tests instead of using --experimental-strip-types juejin-cn/juejin-usage#76

My achievements setting is verified to be completely enabled, and my commit email matches my verified GitHub email exactly.

Could any GitHub Staff member please help escalate this to the backend team for a manual sync? Thank you!

[amasen02]

Hi @Xxcool,

Looking into your profile and the PRs on juejin-cn/juejin-usage (PRs #54, #56, #59, #76), your merged pull request contributions are successfully tracked in GitHub's backend GraphQL API (totalPullRequestContributions: 5), but your achievements pipeline missed the initial minting event.

When an account has not yet unlocked its first achievement badge, https://github.com/<username>?tab=achievements returns HTTP 404 until the achievement worker initializes your badge container.

Why this happens with organization PRs

1. Maintainer Merge Commits: In juejin-cn/juejin-usage, the merge commits themselves were authored by maintainers (wangly19 and ATQQ), while your PR commits used your email (xiabin@data-match.cn). While the PR author is correctly attributed to @Xxcool, the achievement evaluator worker sometimes fails to trigger automatically when the merge commit author is another user in an organization repository.
2. Event-Driven Pipeline: GitHub's achievement calculation does not poll passively; it is triggered by user webhook events (such as a new merge event or profile setting updates). If the initial worker job encountered a transient timeout, it remains idle until a new event occurs.

How to trigger the badge minting

You can force the achievement processor to evaluate your account with these steps:

1. Check Email Verification:
   In GitHub Email Settings, confirm that xiabin@data-match.cn is marked as Verified and has no SSO or domain restriction warnings.
2. Enable Private Contributions:
   In your Public Profile Settings, make sure "Include private contributions on my profile" is checked (organization repositories can sometimes attribute contribution metadata as private depending on org membership settings).
3. Reset the Achievements Toggle:
   Uncheck "Show Achievements on my profile", click Save changes, wait 30 seconds, re-check the box, and save again.
4. Trigger the Achievement Worker with a New Event:
   Merge one more PR into any public repository (or a test sandbox repo like https://github.com/gh-achievements-sandbox).
   The incoming merge webhook forces GitHub's badge evaluation service to recalculate your total merged PR count across all repositories, which will detect your 4 merged PRs and immediately unlock the Pull Shark badge.

[suhasmalur]

You can try checking the Pull Shark achievement requirements first. The PRs need to be merged into the default branch of a repository, and the account must meet GitHub’s achievement criteria.
Since your PRs were merged over a week ago and your profile/verified email settings are correct, this is probably not a normal sync delay.
If the PRs definitely meet the requirements and the achievement is still missing, there doesn't appear to be a user-side option to manually trigger an achievement sync. In that case, GitHub Support would need to investigate the account.

[ssdeniss]

Hey @Xxcool,

Looking at what you've shared I don't think this is something you're obviously doing wrong on your side. You have PRs that were actually merged your achievements are enabled and you've already waited considerably longer than the usual short processing delay.

There have also been a few reports recently from users whose PRs appear to meet the requirements but Pull Shark still doesn't show up so this may be an achievement indexing/processing issue rather than a problem with your profile settings.

A couple of things I would still verify before treating it as a GitHub-side issue:

• Make sure you are the author of each PR and that each one was merged into the repositorys actual default branch (main/master) not only into a release or development branch.

• Check that the PRs are attributed to @Xxcool on GitHub. Since the PR itself is associated with your account I wouldn't focus much on who authored the final merge commit. It's completely normal for a maintainer to merge somebody elses PR.

• Keep Show Achievements on my profile enabled, which you've already confirmed.

• I wouldn't create PRs or repeatedly change settings just to try to "force" the badge. If the existing PRs qualify GitHub should be able to determine that from the existing activity.

I would also be careful with the suggestion above that your accounts "achievement worker missed the minting event" or that merging another PR will definitely force GitHub to recalculate the badge. Unless that behavior is documented by GitHub or confirmed by GitHub staff we can't really know how their internal achievement processing works. Guarantee that a new merge will trigger a re-sync.

At this point you've actually provided most of the information for an investigation: your username, the exact PR URLs the fact that they've been merged for more than a week and confirmation that achievements are enabled.

Since GitHub Support already redirected you here I think the best next step is for a GitHub staff/community team member to check whether these PRs qualify and if they do whether there is an indexing issue affecting your profile.

You may also want to keep the Support ticket/reference number in case a staff member asks for it.

So I wouldn't keep changing things on your account for now. Your case looks very similar to recent Pull Shark reports and if all three PRs were merged into the repositorys default branch this seems worth escalating rather than troubleshooting the same profile settings again.

Hope someone from the GitHub team can take a look, at it for you. 👍

[FriendlyPasser]

I'm experiencing the same issue on my account: https://github.com/FriendlyPasser.

As of September 17, I have 8 merged PRs across 4 repositories, including contributions to other users’ projects. For example:

• test(harness): cover raw result text and failure type serialization Agent-Field/agentfield#1043 — merged into main on September 7.
• docs: clarify virtual environment activation on Windows FriendlyPasser/lecture-to-course#2 — merged on September 13.
• docs: explain how to open courses in a preferred browser FriendlyPasser/lecture-to-course#3 — merged on September 13.

My Quickdraw achievement is publicly visible, but Pull Shark is missing even when I check my achievements while signed in.

Could someone from GitHub help investigate whether these PRs qualify and whether an achievement processing issue is affecting our accounts? Happy to provide any additional details. Thank you!