Pull Shark achievement not awarded despite 6 merged pull requests (2+ weeks since first merge)

[kittimzhe]

🏷️ Discussion Type

Question

💬 Feature/Topic Area

Code Search and Navigation

Body

Hi 👋

My account has never displayed any achievements, even though I meet the Pull Shark eligibility criteria. I'd appreciate it if staff could check whether achievement processing is stuck for my account.

Username: kittimzhe — https://github.com/kittimzhe

Symptoms

• The Achievements section does not render on my profile at all
• https://github.com/kittimzhe?tab=achievements returns 404 (zero badges awarded)
• "Show Achievements on my profile" is enabled in Settings → Profile settings

Qualifying merged pull requests — all authored by me, in public repositories, merged into the default branch:

Pull request	Merged
quarkiverse/quarkus-langchain4j#2749	2026-08-24
apache/dolphinscheduler#18581	2026-08-25
harness/harness#3715	2026-08-26
opensandbox-group/OpenSandbox#1737	2026-09-08
opensandbox-group/OpenSandbox#1774	2026-09-09
opensandbox-group/OpenSandbox#1797	2026-09-10

The earliest qualifying merge was on 2026-08-24, over two weeks ago — well past the usual 24–48h processing window and the 7–14 days after which contacting support is recommended. No badges of any kind have ever appeared on this account, while peers with older qualifying activity do see theirs.

Could someone check whether achievement processing is stuck for this account, or let me know if there's anything else to try? Thanks!

[umairs759]

If your PRs have been merged and you still haven't received the Pull Shark badge after 2+ weeks, the issue is almost always caused by one of the following reasons:

1. Commit Email Mismatch (Most Common):
   The email address configured in your local git client must match an email verified on your GitHub account.

   • Check your commit author email locally:

     git log -1 --format="%an <%ae>"

   • Go to GitHub Settings > Emails and ensure that exact email address is added and verified. If GitHub cannot map the author email to your profile, the PR merges will not count toward achievements.

2. Merged into Non-Default Branch:
   PRs must be merged into the repository's default branch (typically main or master). PRs merged into development branches, staging, or feature branches do not trigger the achievement.

3. Private Contributions Display Setting:
   If the PRs were merged in private repositories, GitHub will not display or credit achievements derived from private repos unless you turn on:

   • Profile Settings > Public profile > Contributions & Activity
   • Check "Include private contributions on my profile".

4. Self-PRs vs. Merged State:
   Ensure the PRs show the purple "Merged" badge rather than the red "Closed" badge. PRs that are closed and manually committed without standard GitHub merge methods do not register.

Check your git commit email against your verified GitHub emails first, as that resolves this in 90% of cases.

[kittimzhe]

Thanks @umairs759! I went through each of these against my account with the API:

• Commit email: every commit I authored across the six PRs (using both my verified personal email and my kittimzhe@users.noreply.github.com noreply address) is correctly linked to my account, so email mapping isn't the issue.
• Default branch: the quarkiverse, harness and OpenSandbox PRs were merged into main; dolphinscheduler#18581 was merged into dev, which is that repository's default branch.
• Private contributions: all six repositories are public, so this doesn't apply.
• Merged state: all six PRs show the purple "Merged" state with merge timestamps.

So none of the common causes apply. The merges span 2026-08-24 → 2026-09-10, zero badges of any kind have ever appeared, and https://github.com/kittimzhe?tab=achievements still returns 404. Could staff check whether achievement processing is stuck for this account? Thanks!

[umairs759]

Thanks for verifying the API data. Since every commit is confirmed linked, merges are on default branches, and repos are public, your account has definitively hit a backend indexing glitch in GitHub's achievement pipeline (where zero-badge accounts fail to initialize the achievements worker).

Because GitHub Community discussions are primarily community-driven and engineering staff do not manually clear individual stuck database queues from discussion threads, here is the exact next step:

Open a direct ticket at GitHub Support:

1. Select Account & Profile → Achievements and contributions.
2. Subject: Achievement calculation pipeline stuck / Zero-badge deadlock.
3. Include your verified username (kittimzhe), the link to this discussion, and mention that your PRs were confirmed merged on default branches via API.

GitHub support agents have internal tooling to trigger a manual recalculation/backfill event for your account, which usually populates the badges within a few hours of their response.