Pull Shark achievement not awarded despite two qualifying merged PRs — possible achievement indexing issue

[coni233]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Profile

Body

Hi GitHub Community / Support,

I'm having an issue with the Pull Shark achievement on my GitHub profile.

My GitHub username is coni233:

https://github.com/coni233

I currently have at least two public pull requests that were created by me and successfully merged into repositories owned by other users:

1. 修复了录入中文名的若干问题 coneypo/Dlib_face_recognition_from_camera#71

   • PR author: coni233
   • Public repository
   • Successfully merged
   • Merged on December 10, 2024

2. fix: 修复开播@列表推送在获取 Bot 成员信息失败时抛异常 Starlwr/StarBot#38

   • PR author: coni233
   • Public repository
   • Successfully merged by the repository maintainer
   • Merged on September 5, 2026

More than 48 hours have passed since the second qualifying PR was merged, but the Pull Shark achievement still does not appear on my profile.

I have also confirmed that:

• Settings → Profile settings → Show Achievements on my profile is enabled.
• Both pull requests were opened by my account, coni233.
• Both repositories are public.
• Both pull requests show a successful Merged status rather than just Closed.
• The second PR was merged by the upstream repository maintainer, not by me.

Expected behavior

My profile should receive and display the Pull Shark achievement after meeting the required merged pull request criteria.

Actual behavior

The Pull Shark achievement has still not been awarded or displayed on my profile.

Could you please check whether there is an issue with the achievement record or achievement indexing for my account?

If the pull requests above are not considered eligible, I would also appreciate clarification on which requirement they do not satisfy.

Thank you for your help.

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

[ryux1]

Both PRs do appear to satisfy the visible conditions: they are public, cross-repository PRs authored by coni233, and they were merged by the upstream maintainers.

The timing is the part that does not match yet. StarBot #38 was merged at 2026-09-05 10:26:55 UTC. This Discussion was opened at 2026-09-07 01:51:45 UTC, only about 39 hours 25 minutes later, not more than 48 hours. The older Dlib PR #71 is already well past any plausible indexing delay, but the second qualifying merge is not.

I would wait until at least 2026-09-07 10:26:55 UTC so the newest merge is actually 48 hours old, then sign out/in and check the profile again. GitHub does not publish a guaranteed achievement-processing deadline, so 48 hours is not an official SLA.

If it is still missing after that, the public data does not reveal an eligibility defect in either PR. At that point this needs GitHub Support to inspect the private achievement index; include both PR URLs and their exact merge timestamps in the ticket: https://support.github.com/request

[coni233]

Thanks for pointing out the timestamp difference. You're right — I miscalculated the 48-hour window. I'll check again after 2026-09-07 10:26:55 UTC, and if the achievement is still missing, I'll contact GitHub Support.

[YugPatelStarDev]

Hey, I think you've already checked most of the important things here.

Both PRs were opened by you, are public, and were actually merged, so if those meet the Pull Shark requirements, it could just be that the achievement hasn't synced correctly yet.

I'd give it a little more time, but since the second PR was merged more than 48 hours ago, I'd probably contact GitHub Support if it still doesn't show up. Include the two PR links and your profile so they can check the achievement data on their side.

Hopefully it's just an indexing delay and gets added soon.

[coni233]

Thank you for checking and for the suggestion!

The second qualifying PR has now been merged for more than 48 hours, and unfortunately the Pull Shark achievement is still missing. I also signed out and back in and checked my profile again, but nothing has changed.

I tried contacting GitHub Support as suggested, but my Support Portal does not appear to provide a general technical support option for Profile/Achievement issues. The available ticket categories are limited, and none of them seem appropriate for an achievement indexing issue.

At this point, since both PRs appear to satisfy the publicly visible requirements, it does seem increasingly likely that this is an achievement synchronization/indexing issue on GitHub's side.

Hopefully a GitHub staff member can take a look at the achievement record for my account or advise me on the correct way to escalate this.

Thanks again for taking the time to help!

[coni233]

Update: The second qualifying PR has now been merged for more than 48 hours, and the Pull Shark achievement is still missing from my profile.

I followed the suggestion to contact GitHub Support, but my Support Portal does not provide a general technical support category for Profile/Achievement issues. The available ticket categories are limited to specific account, billing, repository, and similar issues, and none of the repository ticket options apply to this problem.

Since both PRs appear to satisfy the publicly visible eligibility requirements, could a GitHub staff member please advise whether this can be escalated internally or whether the achievement record/index for my account can be checked?

Profile: https://github.com/coni233

PR 1: coneypo/Dlib_face_recognition_from_camera#71

PR 2: https://github.com/Starlwr/StarBot/pull/38

Show Achievements on my profile is enabled.

Thank you for your help.