Pull Shark achievement not unlocked despite multiple merged PRs

[prashantpiyush1111]

🏷️ Discussion Type

Bug

Body

Hello GitHub Community,

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

My GitHub username is prashantpiyush1111.

In my public repository prashantpiyush1111/AI-Driven-Sales-Forecasting, I have 19 pull requests that were opened by my account and successfully merged.

For example:

• PR Welcome to GitHub product feedback #1 — Merged
• PR Feature Request: Select a column when adding an issue to a project #2 — Merged
• PR Feature request: support release details #3 — Merged
• PR iOS bug report: strange backstack behavior when navigating to a file #4 — Merged
• PR #7 through wLicense #21 — Merged

The repository's Pull Requests page clearly shows these PRs as “by prashantpiyush1111 — Owner — was merged.”

However, the Pull Shark achievement is still not appearing on my GitHub profile, even though I already have many merged pull requests.

Could you please check whether my Pull Shark achievement is not being processed correctly or if there is any eligibility issue with my account?

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

[lucaasporto]

Just wait a bit longer, bro 😄 GitHub can have significant delays when processing badges.

A lot of people have reported this. I actually answered another discussion about the same issue about a week ago, and the person who started that discussion was experiencing a similar delay.

This discussion might be useful for you: PR Badge - Pull Shark delayed by a month · GitHub Community

[Archan47]

The same issue happened to me. I tried this first 2 to 3 weeks ago but didn't get the badge and tried another time but that also didn't work.

[saikatbangla]

Hi @prashantpiyush1111,

Here are the most common reasons why the Pull Shark achievement might not show up despite having merged PRs, along with how to resolve it:

1. Commit Email Attribution (Most Common):
   On GitHub, select one of the merged commits and then click on your username or avatar.
   Unless it is directly linked to your GitHub profile, the email address set in your local git client (git config user.email) will not match the emails that have been verified on your GitHub account.
   To fix this, go to GitHub Settings then select Emails and add the email address that was used in the commits; after it has been verified, GitHub will automatically link your contributions.

2. Integrated into the Default Branch:
   All PRs must be merged directly into the repository's default branch (this is usually main or master); merges into feature or other branches do not count.

3. Anti-Spam / Self-Merge Filters:

   • GitHub's achievement pipeline includes heuristic filters. These filters sometimes ignore quick, back-to-back self-merges on personal repositories to prevent badge automation.
   • Fix: Open a pull request and merge it in another user's public repository or take part in an open-source project. Having a pull request that has been merged by someone external will reliably cause the achievement to be awarded.

4. Profile Visibility Settings:
   Visit your Profile then select Edit profile and make sure that the option called 'Show Achievements on my profile' is turned on.

5. Delay in processing / syncing:
   The jobs for achieving profile achievements are processed asynchronously through cached batch updates and may take between 24 and 48 hours to appear on your profile.

[puneet-zsh]

Hey From what you’ve described it sounds like the PRs being merged alone may not necessarily be enough to trigger the Pull Shark achievement immediately GitHub achievements can sometimes take some time to update and there may also be eligibility requirements around how the PRs were created/merged

If this helps resolve your issue feel free to mark my answer as the accepted answer It would also help me out with the Galaxy Brain achievement 😄

[lucaasporto]

Hi bro! @puneet-zsh

GitHub itself removed the ability to earn this badge through discussions in the Community forum. You can still earn it by answering discussions within a repository.

Here is the announcement made by GitHub: Achievements will no longer be available in the Community

Here is how discussions within a repository work: How to Enable Q&A in GitHub Discussions

If I helped you, please click the arrow button below to upvote the answer. Thanks!

[puneet-zsh]

Ahh got it bro I wasn't aware that GitHub removed achievements from the Community forum Thanks for pointing me in the right direction Appreciate it! 🙌