Pull Shark achievement stuck at x2 despite 141 merged pull requests

[Rene-Kuhm]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Profile

Body

Hello GitHub Support / Community team,

My Pull Shark achievement appears to be stuck at Bronze (x2), although my public activity has passed the documented community threshold for Silver (x3).

Account: @Rene-Kuhm
Achievements page: https://github.com/Rene-Kuhm?tab=achievements
Public merged PR search: https://github.com/pulls?q=is%3Apr+author%3ARene-Kuhm+is%3Amerged
Current public total: 141 pull requests authored by me and merged.

Timeline and evidence:

• There were 125 public merged PRs before 2026-08-02.
• On 2026-08-02, 16 additional PRs were merged.
• The PR that brought the public chronological count to 128 was fix(usb): stop tearing down the listener on a recoverable Overflow Rene-Kuhm/redragon-streamdeck-linux-#18 at 2026-08-02T14:39:46Z.
• That PR was authored by @Rene-Kuhm and merged into the repository default branch, main.
• The other PRs in that batch were also authored by me and merged into main.
• More than 24 hours later, the public achievement detail still reports tier-count 2 and only displays Pull Shark x2.

Troubleshooting already performed:

• Achievements are enabled and publicly visible.
• The relevant PRs are merged, not merely closed.
• The threshold-crossing repository is not a fork.
• The threshold-crossing PR targets the default branch.
• The profile was checked directly and outside the normal browser cache.
• I searched for similar reports, including discussions Achievements not getting updated #41755 and Achievments not Showing #67590.

Could you please check whether the achievement counter is delayed, confirm which PRs are considered eligible, or trigger a recalculation for the account?

Thank you.

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