Pull Shark achievement missing despite 17 merged public PRs #209607
🏷️ Discussion TypeBug 💬 Feature/Topic AreaProfile BodySummaryMy account, @fukalous, has no Achievements section even though GitHub recognizes substantial qualifying public activity. Evidence checked
Representative merged PRs:
Expected behaviorThe profile should show any earned achievements. This level of merged public pull request activity is normally associated with the Pull Shark achievement. Actual behaviorThe public profile has no Achievements section and no badge has appeared after several days. Support contextGitHub Support ticket #4826697 was created with the same evidence, but Standard-account support automatically closed it and directed me to GitHub Community resources. Could GitHub staff confirm whether this is an achievement eligibility/indexing issue and whether the account needs to be reprocessed? |
Replies: 5 comments
|
💬 Your Product Feedback Has Been Submitted 🎉 Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users. Here's what you can expect moving forward ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities. Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐ |
|
This looks like an achievement indexing/eligibility issue rather than a contribution issue. Since the merged PRs are already counted and several days have passed, GitHub may need to reprocess the account for achievement eligibility. Hopefully GitHub staff can confirm whether there’s an indexing delay or account-specific issue. I also came with this issue, after 24 -48 hour, the achievement will appear in your profile. |
|
Your PRs all qualify. Pull Shark bronze only needs 2 merged PRs into public non-fork repos, and you've got 17. Your settings are right too. This is GitHub's achievement backlog, not your fault. The system has been slow since September, and a bunch of people with way more than enough PRs are waiting. Your 27 PR contributions are counted, the badge just hasn't been issued yet. Nothing to fix on your end. It'll show up once their processing catches up. |
|
THANK YOU all, this problem has been solved! |
|
Live-verified just now: the search API ( Two corrections to what's above: The 24-48h expectation no longer holds. This is part of a staff-confirmed backfill delay running since late September — ebndev's Sep 23 statement (marked answer in #208263): internal teams investigating, "delays of several days", explicitly no timeline. The aggregation thread #203416 has users who've been waiting three weeks and counting; my own data points: two achievements triggered Sep 18 and Sep 25 are still pending on my profile today. "Slow since September" is right, but the honest number is weeks, not 24-48 hours. Why your Achievements section is missing entirely rather than just incomplete: the section only renders once an account has at least one earned badge. Yours has zero issued badges — the Pull Shark that would seed the section is itself stuck in the pipeline. So "no section" and "badge not awarded" are the same defect here, not two. What to do: add your username and the merge dates (Sep 29 – Oct 2) to #203416 — that's the thread staff are using to aggregate affected accounts, and backfill is batch when it lands. Nothing to fix repo-side; your GraphQL evidence is exactly the right bundle to cite if you end up needing a support ticket after the pipeline recovers. |
Live-verified just now: the search API (
author:fukalous type:pr is:merged) returns 20 merged PRs across eight public repositories (SurfSense ×12, FlashRAG ×2, funes, briefcase ×2, Soup, OpenViking, ms-swift) — ten times the Pull Shark base tier. Your settings and evidence are all in order, so this isn't eligibility.Two corrections to what's above:
The 24-48h expectation no longer holds. This is part of a staff-confirmed backfill delay running since late September — ebndev's Sep 23 statement (marked answer in #208263): internal teams investigating, "delays of several days", explicitly no timeline. The aggregation thread #203416 has users who've been waiting three weeks and counting; my ow…