Pull Shark and YOLO not awarded despite qualifying public activity

[sheldon-lang]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Profile

Body

What I was trying to do

Earn the Pull Shark and YOLO achievements on my public profile.

What I expected

• Pull Shark should be awarded after multiple pull requests were merged into default branches.
• YOLO should be awarded after merging a pull request with no code reviews.

What happened instead

My profile has achievements and private contributions enabled, but only Quickdraw is displayed. The Achievements tab also shows only Quickdraw.

Public merged pull requests include:

• Add opt-in per-stream session IDs for Weka subagents kubernetes-sigs/inference-perf#874
• Report request session IDs in lifecycle metrics kubernetes-sigs/inference-perf#898
• Drop scheduled-ahead requests during stage teardown kubernetes-sigs/inference-perf#905
• Fix GLM-5.3 GB300 Rust reasoning parser image vllm-project/recipes#1123

The earliest of these was merged on 2026-10-13, so this is well beyond the commonly reported 24-48 hour synchronization window. All PRs are publicly attributed to @sheldon-lang.

For YOLO, I opened and merged this public PR with no code review:
sheldon-lang/anxinai-community#2

Related discussions

• https://github.com/orgs/community/discussions/210474
• https://github.com/orgs/community/discussions/210967
• https://github.com/orgs/community/discussions/210305

Questions

Are these achievements delayed, or is automatic awarding currently failing? If self-opened/self-merged PRs are excluded from YOLO, can GitHub clarify that rule in the documentation? If they are eligible, can the missing achievement credit be reviewed?

I searched for similar discussions before posting.

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