Pull Shark not working after making enough pull requests.

[Jakubic769]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Code Search and Navigation

Body

The pull shark achievement is not working. I should have received it with my second merged PR into a public repository, but i didn't. I already looked for bug reports here so can say that i already took care of looking into the suggested possible solutions.

I already double checked that those PR are fully merged in their respective repositories.

Jakubic769/OsuFinder#5
Jakubic769/terminal-pong#3

I already checked that the show achievements option is on.

I already looked if it was given to me, but hided by default.

Other contributors are having the same issue. Any help with my shark? Thank you kindly.

[Jakubic769]

what?

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

[Hacka-Gotchi]

It can take some time for GitHub achievements to update and appear on your profile. I’d give it a few more days and check again.

Especially pull shark

[TongyiDai]

The concrete difference in your examples is ownership/merge identity, not processing delay. I checked the referenced PRs: they were authored by Jakubic769 and merged by Jakubic769 into repositories owned by Jakubic769, with no reviews.

That activity is useful for normal repository development, but it does not establish the unambiguous “another maintainer merged my contribution” pattern associated with Pull Shark. GitHub does not publish a complete badge-eligibility specification, and recent reports show that not every self-authored/self-merged PR in a personal repository advances the badge even though the PR page says Merged.

The clean test is therefore:

1. Make two genuine pull requests to standalone public repositories you do not own.
2. Ensure the PRs are authored by your account.
3. Have the repository maintainers merge them into the default branch.
4. Wait for achievement processing and keep Show Achievements on my profile enabled.

Do not create artificial upstream PRs solely for the badge; choose small documentation, test, or bug-fix contributions that the projects actually need.

If two qualifying upstream merges still do not produce Pull Shark after several days, send GitHub Support those two PR URLs. At that point they are much stronger evidence of an indexing problem than personal self-merges.