Pull Shark still x2 after 128 merged PRs, please reindex

[ZYZ666-RGB]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Profile

Body

My GitHub username is ZYZ666-RGB. Pull Shark is still bronze x2, and the official badge history only lists the 2nd merged PR ([#2](ZYZ666-RGB/crafthub-ai#2)) and the 16th ([#12222](apache/seatunnel#12222)). There is no 128th row. Search currently shows 141 merged PRs I authored ("author:ZYZ666-RGB is:pr is:merged"). The 128th by merge time is [#5380](pipeshub-ai/pipeshub-ai#5380), merged at 2026-11-06T13:01:19Z, almost 7 days ago, with more merges since. Other achievements on this account are updating (Galaxy Brain appeared today), but Pull Shark has not upgraded to x3. Please reindex achievements for this account.

[github-actions[bot]]

💬 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 ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

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

[100rootrain]

Achievements aren't granted at merge time right now. They're recalculated in the background, and recent tier upgrades have taken 4–7 days (in #212684 the threshold was reached Nov 5 and the tier unlocked Nov 10). Your 128th merge was Nov 6 13:01 UTC, about 6.8 days before you posted, so this may still be the normal delay. Galaxy Brain showing up today doesn't rule that out, since each achievement is processed separately.

One thing worth checking before waiting longer, though: I can only find 48 of your 141 merged PRs publicly. The same search through the API, which only sees what's visible to everyone, returns:

https://github.com/pulls?q=is:pr+author:ZYZ666-RGB+is:merged

• 48 merged, 92 open, 15 closed without merging (155 in total)
• Sorted by merge time, pipeshub-ai/pipeshub-ai#5380 is the 44th, not the 128th

Your profile also shows no private contributions, and its 155 PR contributions match the public PRs exactly. So the other ~93 merged PRs are only visible when you're signed in, most likely because they're in private repositories. GitHub doesn't document whether PRs in private repos count toward Pull Shark. If they do, this is just the delay. If they don't, the achievement's count is around 48, x2 is the expected tier, and waiting won't change it.

To tell which it is:

1. Open the search above in a private/incognito window. If it shows 48 instead of 141, the rest aren't public.
2. Give it until about Nov 16–17 (10 days after the 128th merge). If it's still x2 by then, add the 48 vs 141 numbers to your post. "48 of my merged PRs are public and the other 93 are in private repos. Do those count?" is a question staff can actually answer, unlike a general reindex request.

Related: #212684 (why the history lists only one PR per tier), #212220 (processing delay)

[ZYZ666-RGB]

Thanks for checking the public vs private split — the 48 public merged PRs vs the rest in private repos matches what I see too.

On whether private-repo PRs count: I compared with a colleague whose profile shows Pull Shark x3 (the 128 threshold). A public search only finds 2 merged PRs by them (is:pr author:Torturedman is:merged is:public). If private PRs were excluded, they could not have reached x3. So private merged PRs do appear to count, and my case is more likely the reindex delay you described.

I'll wait until around Nov 16–17 as you suggested, and will add the 48 vs 141 numbers if it's still x2 then.