Happened to me, no need to worry, it just takes time sometimes

if it still doesn't appear by the beginning of next time, worth a support ticket from github

The important distinction here is that having 3 merged pull requests does not necessarily mean the Pull Shark achievement will immediately be awarded.

The is:pr author:fadilasif is:merged search confirms that the PRs were merged and authored by the account, but that alone doesn't necessarily establish that GitHub's achievement system considers all of them eligible.

A few things I would check:

Were the PRs actually merged into the default branch?
The achievement is based on qualifying merged pull requests, so it's worth checking the individual PRs and the branch they were merged into.
Are the repositories eligible for achievements?
GitHub's achievement system has eligibility rules for repositories and contributions. A PR being publicly visible and merged does not automatically mean every repository/PR contributes toward an achievement.
Check the PR author's account carefully.
Make sure the PR was opened from the same GitHub account (@fadilasif) that you're checking the achievement on, rather than being associated with another account/email.
Allow some time for the achievement system to update.
Achievements aren't necessarily updated immediately after an event. If the PRs were merged recently, I'd give GitHub some time before assuming something is broken.

I'd also try checking the achievement page directly rather than relying only on the profile display. If the PRs were merged a while ago and all of the repositories/PRs satisfy the eligibility requirements, but Pull Shark still doesn't appear, then this could be worth reporting as an achievement/account issue to GitHub Support.

One other thing I'd avoid relying on is simply the number of merged PRs returned by the search query. The search query answers "which PRs match these search conditions?", whereas the achievement system determines "which contributions count toward this achievement?" Those aren't necessarily identical sets.

So in this case, I would first verify the eligibility of each of the three repositories/PRs and then wait for the achievement system to update before concluding that the achievement is missing.

Hi @fadilasif!

Since you already have 3 merged PRs in public repositories, you have definitely met the numeric threshold for the achievement—the base Pull Shark badge only requires 2 merged PRs.

If the badge isn't showing up on your profile, you likely haven't done anything wrong. Here are the most common reasons why this happens and what to check:

1. Processing Delays (Most Common)

GitHub’s achievement system does not update instantly. It runs in background batches, meaning it typically takes 24 to 48 hours for a badge to appear after your qualifying PR is merged. During periods of high load or backend issues, some users have reported waiting up to a couple of weeks for it to sync.

2. The "Default Branch" Rule

This is the most common technical reason that valid-looking PRs don't trigger the achievement. To count toward Pull Shark, your PRs must be merged into the repository's default branch (usually main or master).

• If the maintainers of lgse/strata or anishfn/omarchy-widgets merged your PRs into a dev, staging, or feature branch, those merges will not count toward the badge.

3. Squash Merges & Email Attribution

If a maintainer uses "Squash and merge" to approve your PR, GitHub needs to properly recognize you as the author of that final squashed commit.

• Ensure the email address you use in your local Git environment (git config user.email) is added and verified in your GitHub Email Settings. If it isn't, GitHub might credit the final code to the maintainer who clicked merge, even though you are listed as the PR author.

4. The Repository Cannot Be a Fork

PRs merged into a repository that is itself a fork of another project do not count toward Pull Shark. While lgse/strata and anishfn/omarchy-widgets appear to be root public repositories, this is a strict rule to keep in mind.

What you should do next:

• Give it time: If it’s been less than 48 hours since the merges, just wait for the system to catch up.
• Verify the target branch: Look at your 3 merged PRs and confirm they were merged directly into main or master.
• The Toggle Trick: Sometimes the UI gets stuck. Go to your GitHub profile, click Edit Profile, scroll down to the Achievements section, toggle the setting to hide achievements off, save, and then turn it back on to force a refresh.

If you verify that all your PRs went to the default branch with a verified email and it has been more than a week, you can safely open a ticket with GitHub Support to ask them to sync your profile.

Congratulations on the merged PRs!

1. Support Ticket Category for Achievements / Profile Issues

• Select Account, Profile, and Security > Profile or Dashboard (or Account / Billing > General Account Issue if profile-specific categories are unavailable). If there is no dedicated "Achievements" dropdown, select the general profile issue option and specify that your profile badges are not syncing in the ticket description.

2. Resolving the 404 Error on the Achievements Section

• Check the URL Format: Ensure you are navigating directly to [https://github.com/fadilasif?tab=achievements](https://github.com/fadilasif?tab=achievements) while signed into your account rather than following a broken relative path.
• Toggle Profile Settings: Go to Settings > Profile, find the Achievements checkbox, uncheck "Show Achievements on my profile," save, and re-enable it to force a UI refresh.
• Clear Cache / Incognito: Test opening your profile in an Incognito/Private window or clear your browser cache to resolve stale routing errors.

3. Common Reasons the Pull Shark Badge Is Delayed or Missing

• Processing Backlog: Background updates for GitHub achievements routinely take 24 to 48 hours (and occasionally longer during site maintenance) after a PR is merged.
• Merged Branch Eligibility: PRs must be merged directly into the repository's default branch (e.g., main or master). Merges into development (dev), staging, or non-default branches do not trigger the badge.
• Squash Merges & Email Matching: If the maintainer used "Squash and merge," ensure the email associated with the commits matches a verified email on your GitHub account so author attribution is retained.
• Repository Type: Merged PRs inside a forked repository do not count toward the achievement; they must be merged into a standalone public repository.

Pull Shark has a few requirements beyond just having merged PRs. The PRs need to be merged in eligible public repositories, and the achievement may take some time to update.

I'd first check that all three PRs are actually merged and that the author is the same GitHub account. If everything looks correct, it could simply be a delay in the achievement system.

You could also try checking your achievements page again later or opening a GitHub Support ticket if it still doesn't appear.