Pull Shark achievement not appearing despite 3 merged pull requests

[Amir-hkr]

🏷️ Discussion Type

Question

💬 Feature/Topic Area

Profile

Body

Hello,

I think there may be an issue with my GitHub achievements.

My profile: https://github.com/Amir-hkr

I have three public pull requests that have been successfully merged into upstream repositories. I have already received the Quickdraw and YOLO achievements, but Pull Shark does not appear on my Achievements page at all.

The merged pull requests are:

• [Need support]: Add a test guarding relative markdown links mloda-ai/mloda-plugin-template#88
• docs: improve public issue templates nanlabs/aws-glue-etl-boilerplate#66
• docs: fix step reference in setup section mloda-ai/mloda-plugin-template#89

Is this expected behavior, or could there be an issue with my account or the achievement system?

Thank you!

[jaiganesh2108]

Hi! It doesn't necessarily indicate a problem with your account.

The Pull Shark achievement can sometimes take a while to appear after a qualifying pull request is merged. Also, not every merged PR is guaranteed to qualify, as GitHub hasn't documented all of the eligibility criteria for achievements.

Since you've already received Quickdraw and YOLO, it looks like your achievements are being processed normally. I'd recommend waiting a few more days if the merges were recent. If the badge still hasn't appeared after a reasonable amount of time, it's worth contacting GitHub Support so they can check whether those merged PRs were eligible or if there's an issue with the achievement system.

Hopefully it shows up soon!

[anurag-samal]

Try creating a demo repo on your account, push some initial code or text / markdown ( even a simple readme.md will do the work).
Create a separate branch ( you can name it as dev) change something and push to dev.
Open a pull request and merge the request from dev -> main.

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