Pull Shark & other achievements missing despite three qualifying merged PRs

[mig-builds]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Profile

Body

Problem

The Pull Shark achievement is not appearing on my GitHub profile even though I have authored three qualifying pull requests that were merged into the default branches of public, standalone repositories.

GitHub account

mig-builds

Qualifying merged pull requests

1. fix: localize agent stats panel antropos17/Aegis#273
2. fix: balance dashboard chart layout Harsh-vardhan09/AthLead#103
3. chore: add pre-commit formatting and lint checks Harsh-vardhan09/AthLead#94

For each pull request:

• I am the PR author.
• The repository is public and is not a fork.
• A repository maintainer merged the PR.
• The PR was merged into the repository’s default branch.
• The PR is shown as Merged, not merely closed.

Troubleshooting completed

• Show Achievements on my profile is enabled.
• I disabled the setting, saved it, signed out, signed back in, enabled it again, and saved it.
• I checked my profile in a private/incognito window.
• The most recent qualifying merge is several days old, so I have waited longer than the usual profile-processing period.
• My public profile still has no Achievements section.

GitHub Support response

I contacted GitHub Support, but my ticket was automatically closed because my available support options are limited to Community Discussions, GitHub Docs, and GitHub Skills.

Expected result

The qualifying merged pull requests should be recognized and the Pull Shark achievement should appear on my profile.

Request

Could someone confirm whether these PRs meet the current eligibility requirements and whether this appears to be an achievement-processing or account-attribution issue?

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

[satiricalguru]

I verified your qualifying pull requests (antropos17/Aegis#273, Harsh-vardhan09/AthLead#94, and Harsh-vardhan09/AthLead#103):

1. Eligibility is 100% Valid:
   • The repositories are public and not forks.
   • The PRs were merged into their respective default branches (master and main) by maintainers.
   • The commit author email (54319294+mig-builds@users.noreply.github.com) matches your GitHub account attribution.

---

Why the Pull Shark badge hasn't appeared yet

GitHub Achievements are processed by asynchronous background workers rather than synchronously at the moment of merge. There are two primary reasons why the badge section may experience a delay:

1. Background Indexing Queue Lag:
   The achievement evaluation pipeline periodically processes account badges in batches. During platform queue backpressure, badge reconciliation can lag behind the contribution graph updates.

2. Profile Sidebar Cache Invalidation:
   The public profile sidebar caches achievement state. The section only appears once the cache renders the unlocked badge.

---

Recommended Actions to Force a Profile Refresh

1. Trigger a Profile Cache Invalidation:
   • Go to Settings > Profile, make a minor update (e.g., add a temporary character or update your Bio/Location), and click Update profile. This often forces the profile UI cache to re-render.
2. Trigger a Re-indexing Event:
   • Creating another commit or opening/merging a small PR often prompts the GitHub contribution/achievement worker to re-evaluate the full account history and flush pending badges.
3. Confirm Settings:
   • Double check under Settings > Profile that Show Achievements on my profile remains checked.

Since your PRs meet all criteria, your account is fully eligible, and the badge will display as soon as the background worker runs its batch sync on your profile.

[mig-builds]

Thanks for the prompt response and support. I tried all the suggestions options. but still it does not show the achievements. Could you please check what could be the issue? @satiricalguru

[sushant-me]

Three merged PRs exceed the Pull Shark threshold (2), so one of these usually explains it: 1) Verified email - the commit email must be a verified email on your GitHub account; check the commits in your merged PRs. 2) Default branch - PRs must be merged into the base repo's default branch; merges into other branches or work left in forks do not count. 3) Author - automated merges by bots (Dependabot etc.) do not count because you are not the author. 4) Private repos - they count only if you enabled 'Show private contributions and achievements'. 5) 24h processing delay - wait a full day, then check in an incognito window. If all of these check out and it still has not appeared, contact GitHub Support with links to the merged PRs.