Pull Shark achievement not awarded despite 7 merged pull requests

[hyy321]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Profile

Body

Hi GitHub Community,

My GitHub username is @hyy321.

I’m experiencing an issue where the Pull Shark achievement is not appearing on my profile, even though I currently have 7 pull requests authored by my account that have been successfully merged into public upstream repositories.

Some of the merged pull requests are:

• fix(monitor): ignore unrelated files when loading cache Project-HAMi/HAMi#2529
• docs: update vGPU memory metric documentation Project-HAMi/website#738
• fix(diff): propagate untracked file listing errors alibaba/open-code-review#1140
• fix(ci): handle deleted changelog files rustsbi/rustsbi#265
• feat(viewer): add back navigation to improve page traversal UX alibaba/open-code-review#1217
• feat(allowlist): exclude secret paths from review alibaba/open-code-review#1262
• feat(allowlist): protect per-environment .env files alibaba/open-code-review#1279

I have already verified that:

• “Show Achievements on my profile” is enabled.
• The pull requests were authored by my GitHub account.
• The pull requests were successfully merged.
• The repositories are public.
• The pull requests were merged into their repositories’ default branches.
• My commit email is verified and associated with my GitHub account.
• Other achievements, such as Quickdraw, are visible on my profile.

I can also confirm the merged PRs using the GitHub search:

is:pr author:hyy321 is:merged

Could someone please confirm whether there is currently an issue or delay with the Pull Shark achievement system, or whether I may be missing another eligibility requirement?

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

[TongyiDai]

I checked all seven linked pull requests. GitHub reports hyy321 as the PR author, each PR as merged, and each merge target as that repository's current default branch. The source repositories are forks, but the seven target repositories are not. The public profile still shows Quickdraw and not Pull Shark.

Four merges are very recent (September 8 and September 15), but the two August merges are already well beyond an ordinary short processing delay. The publicly verifiable eligibility signals therefore look consistent; this is not explained by a missing verified email because Pull Shark is based on authored pull requests, not commit-author email attribution.

This matches the unresolved profile/achievement rendering incident tracked in #203416. I would add your account and two oldest qualifying PRs there so staff can correlate the affected profile without duplicating all seven links. Include the date you confirmed Show Achievements is enabled and note that Quickdraw renders correctly, which helps distinguish a global visibility setting from a Pull Shark indexing failure. There is no user-facing achievement reindex control, so repeatedly opening or merging test PRs is unlikely to be useful.