Github acheivements issue

[SAHAJCSE]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Issues

Body

Title: Pull Shark & Pair Extraordinaire achievements not showing

Hi everyone,

I've created and merged multiple pull requests and also used co-authored commits where required, but I still haven't received the Pull Shark or Pair Extraordinaire achievements.

Is there a delay in awarding these badges, or am I missing any eligibility requirements?

Any help would be appreciated. Thanks!

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

[Mr-Nilarnab]

@SAHAJCSE

GitHub Achievements are awarded automatically, but they aren't always updated immediately. In many cases there's a delay between completing the qualifying activity and the achievement appearing on your profile.

A few things to verify for the two achievements you mentioned:

Pull Shark

• The pull request must be merged (not just closed).
• It must be merged into the repository's default branch or another qualifying branch.
• The contribution must be associated with your GitHub account.

Pair Extraordinaire

• Your contribution must be made using a properly formatted co-authored commit, for example:

Co-authored-by: Full Name <username@users.noreply.github.com>

or another email address that is verified on the co-author's GitHub account.

If the Co-authored-by trailer is missing, incorrectly formatted, or uses an email that isn't linked to the GitHub account, the contribution may not be recognized.

A few questions that may help identify the issue:

• Approximately when were the qualifying PRs merged?
• Are the repositories public or private?
• Can you confirm that the co-authored commits appear correctly on the commit page?
• Have you received any other GitHub Achievements recently, or is this affecting only these two?

If everything appears to meet the requirements and it's been several days since the qualifying activity, it may simply be an indexing delay or an issue with the achievements service. In that case, sharing links to one merged pull request and one co-authored commit (if they're public) would help others verify whether they meet the expected criteria.

[v-ember]

Hey there! 👋

Thanks for posting in the GitHub Community, @SAHAJCSE ! You are more likely to get a useful response if you are posting in the applicable category. The Accessibility category is a place for our community to discuss and provide feedback on the digital accessibility of GitHub products. Digital accessibility means that GitHub tools, and technologies, are designed and developed so that people with disabilities can use them.

I've gone ahead and moved this to the correct category for you. Good luck!

[KhyFee]

Agree with @Mr-Nilarnab on the core rules (merged into default branch, verified email, co-author trailer format for Pair Extraordinaire).

For Pair Extraordinaire specifically: the merged commit needs a real second person via:

Co-authored-by: Name <email@example.com>

…and that email should be linked to a GitHub user. A solo “co-author” with a fake address usually won’t unlock it.

For Pull Shark: if merges are already days old and the achievements tab is empty for those badges, treat it as possible backend delay/glitch — toggle Show Achievements off/on once, then if still missing after 72h, Support with PR links helps more than re-merging the same work.

[ANEWCAN]

I have encountered the same problem and am looking forward to receiving a response.

[KhyFee]

Pull Shark / pair achievements — practical checks

GitHub doesn’t document exact thresholds publicly, and grants can lag. When Pull Shark / Pair Extraordinaire lag or vanish, work through this:

1. Merged vs closed — only merged PRs count. “Closed” without merge does not.
2. Fork PRs into the base repo — you need merges on the upstream public project, not only merges on your fork’s default branch.
3. Author is you — co-authored-by can help Pair Extraordinaire when a different real person co-authors; it won’t invent Pair Solo for self-merges alone.
4. Achievements enablement — Profile → Customize / settings: show achievements. Private contribution toggles affect messaging but public merges should still populate public sharks.
5. Lag — days of delay is common after a merge. If the achievements tab itself 404s, that’s often a temporary/profile flags issue — Support is the right place; community can only checklist.
6. Gaming / spam merges to farm sharks often gets ignored by the pipeline. Real external merges are the durable path.

If you’ve got ≥ a handful of real external merges and still no shark after a week+, include links to the merged PRs (not just a count) when you ping Support.

[ebndev]

Hi! We appreciate you reaching out to report this issue.

We have provided details about the incident in this discussion.

To keep conversations all in one place and to ensure you receive timely updates, we’ll be closing this post and recommend you comment on or subscribe to the discussion linked above.

We appreciate your patience as we work toward a solution.