Pull Shark not awarded after 33 merged pull requests since March, including four merged by another maintainer

[DRAZY]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Code Search and Navigation

Body

My profile (https://github.com/DRAZY) shows Quickdraw, Starstruck and YOLO, and YOLO appeared on 13 September 2026, so the achievements job is running for my account. Pull Shark has never appeared.

I have 33 merged pull requests on public repositories, the first on 17 March 2026 and the latest on 15 September 2026, across six repositories. The search is:pr is:merged author:DRAZY lists them all. Four of them were merged into a repository I do not own by its maintainer back in June (needmorecowbell/drawfinity, pull requests 59 to 62), so this is not only self-merged pull requests in my own repositories. The other 29 are merged into the default branch of my own public repositories (deemix-remastered, Audio-V, claude-skills, noctura-screensaver, TuberX).

"Show Achievements on my profile" is enabled. GitHub Support closed my ticket (#4765409) because my plan has no technical support and pointed me here. My earlier post #208069 was auto-closed for not using this form, so this is the resubmission.

This looks like the same thing reported in #207838, #207991, #207122 and #207112 over the past two weeks. Is there anything about these pull requests that would disqualify them, or is the Pull Shark evaluation stuck for a set of accounts right now?

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