Pull Shark achievement not showing after 13 merged PRs

[ItsDeadlyProgrammer]

🏷️ Discussion Type

Question

💬 Feature/Topic Area

Profile

Body

Hi everyone,

I've had several pull requests merged over the last week, but I still haven't received the Pull Shark achievement. The only one on my profile is Quickdraw.

Username: @ItsDeadlyProgrammer (https://github.com/ItsDeadlyProgrammer)

Some of the merged PRs:

• Allow IPv6 addresses as proxy host AntennaPod/AntennaPod#8835 (merged 2026-10-11)
• Fix #1756: decode multi-byte UTF-8 char after backslash in async parser FasterXML/jackson-core#1759 (merged 2026-10-11)
• fix(mockk): dispose stubs removed by clearAllStubsFromMemory mockk/mockk#1567 (merged 2026-10-11)
• Do not treat maxContains < minContains as a schema error networknt/json-schema-validator#1295, #129, #1306 (merged 2026-10-12/13)
• fix(core): show the name of the <test> in the executor log line testng-team/testng#3581 (merged 2026-10-13)
• Keep the original error as the cause of a failed permutation kotest/kotest#6251, Read the plugins of an Extension annotation inherited from a superclass (fixes #701) pf4j/pf4j#708 (merged

All of these show the purple "Merged" label d and then applied by hand. They're all inpublic repos and opened from my own account.

Things I've already checked:

• "Show Achievements on my profile" is turnefile
• Private contributions aren't involved, since all the repos are public
• It's been about 6 days since the first two

Is there a delay before Pull Shark gets awar it on my account? Thanks for any help.

[Jack-Waller]

This may be due to an ongoing incident with delays to achievements.

[0x9z]

Hi @ItsDeadlyProgrammer,

You've already done the right checks (public repos, merged status, achievements enabled). Based on the PRs you listed and recent reports from other users, there are a few likely explanations:

[0x9z]

1. Known GitHub-side delay (most likely):
   GitHub staff have confirmed there are ongoing delays affecting when achievements appear on profiles, sometimes lasting several days or longer . Your merges are from Oct 11–13, and you posted Oct 17, so you're right in that window. Several users with PRs merged in the same period reported the same issue.

[0x9z]

2. Anti-spam / self-merge filters
   GitHub's achievement pipeline uses heuristic filters that can silently ignore rapid back-to-back merges, especially in personal repos. Your PRs into established projects like AntennaPod, jackson-core, and mockk should count, but if the system flagged the burst of activity, it may just need time or a "trigger" from an external merge.

[0x9z]

3. Verified email attribution
   Double-check that the email in your local git config matches a verified email on your GitHub account. If a squash/rebase merge rewrote authorship, GitHub may not attribute it to you.

[0x9z]

this is almost certainly a processing issue on GitHub's end, not something you did wrong. Just give it 1–2 weeks from your first merge (Oct 11), since Pull Shark is taking 2–3 weeks for a lot of people in 2026. If you want to nudge it, merge one more PR into someone else's repo (not your own) — it often kicks the pipeline back into gear — and toggle achievements off/on in Settings → Public profile to force a cache refresh. If nothing after ~2 weeks, open a Support ticket with your PR links and mention the known delay. You're good. 👍