Pull Shark
Summary
Pull Shark is an active, tiered GitHub profile achievement associated with authored pull requests that are merged. GitHub presents achievements in the profile sidebar and may link an achievement to qualifying events when the viewer has access to the relevant repository.
Trigger
GitHub’s live achievement detail states that Pull Shark recognises pull requests opened by the account that have been merged.
GitHub does not publish every internal attribution filter. Treat repository visibility, deleted repositories, transferred repositories, account changes, and historical recalculation behaviour as implementation details unless GitHub documents them.
Progression and tiers
GitHub’s live x4 achievement history publishes the following milestone ordinals.
| Level | Reported threshold | Evidence status |
|---|---|---|
| Base achievement | 2 merged pull requests | Official |
| Bronze | 16 merged pull requests | Official |
| Silver | 128 merged pull requests | Official |
| Gold | 1,024 merged pull requests | Official |
A threshold should not be described as reached solely from a manually counted total. GitHub’s internal eligible-event count may differ from a user’s own search results.
Eligibility conditions
- The pull request must be merged rather than merely opened or closed.
- The account seeking the achievement must be recorded as the pull request author.
- The merge must be associated with GitHub.com achievement processing.
- Private or internal activity may affect achievements according to the account’s contribution and achievement visibility settings.
- Event details are only visible to viewers who can access the repository or organisation where the event occurred.
The effect of repository deletion, repository transfer, author-account migration, bot authorship, and imported history remains insufficiently documented for firm guarantees.
Award timing
Awarding and tier changes may not appear immediately after a qualifying merge. GitHub does not publish a service-level target for achievement processing.
When a threshold appears to have been reached, allow for asynchronous processing before treating the badge as missing.
Verification
- Open your GitHub profile and inspect the Achievements section.
- Select the Pull Shark badge to view its current presentation and any linked contributing events.
- Confirm that the relevant pull requests show your account as author and have a merged state.
- Review Settings → Profile settings to ensure achievements are enabled.
- Review contribution settings if private or internal activity is relevant.
Do not publish screenshots that expose private repository names, organisation names, billing data, tokens, email addresses, or inaccessible event URLs.
Evidence status
| Claim | Status |
|---|---|
| GitHub displays achievements on user profiles | Official |
| Achievement event links depend on repository or organisation access | Official |
| Achievements can be hidden globally or individually | Official |
| Pull Shark recognises opened pull requests that are merged | Official |
| The four numerical thresholds in this guide | Official |
| Exact processing delay | Unknown |
| Exact handling of deleted, transferred, imported, or migrated history | Unknown |
Known limitations and edge cases
- A user’s visible pull-request count is not necessarily GitHub’s eligible achievement count.
- Closed but unmerged pull requests do not satisfy the documented trigger used by this guide.
- Achievement visibility settings can make an earned badge appear absent to other viewers.
- Private-profile settings can hide achievements and highlights.
- Links from an achievement may be inaccessible to viewers without repository access.
- GitHub labels achievements as a public-preview feature, so behaviour can change without the tier table being formally versioned.
Troubleshooting
If Pull Shark or a new tier does not appear:
- Confirm each relevant pull request is merged.
- Confirm your account is the pull-request author, not only a reviewer, committer, or merger.
- Check that achievements are enabled in profile settings.
- Check whether the profile or individual achievement is hidden.
- Allow time for profile processing and refresh the profile later.
- Avoid assuming that every result returned by a pull-request search is eligible.
- Record reproducible evidence and the date observed before reporting a possible threshold or platform defect.
Responsible participation
Earn Pull Shark through useful, independently reviewable contributions. Suitable work includes documentation corrections, tests, accessibility improvements, maintenance, bug fixes, and focused feature changes.
Avoid empty pull requests, duplicate edits, artificial repository splitting, misleading changes, or deliberately noisy history created only to increase a counter.
History
GitHub announced profile achievements as a public beta on 9 June 2022. Pull Shark appeared among the achievements shown in that launch material.
GitHub’s live x4 detail fragment exposes the complete milestone history at the 2nd, 16th, 128th, and 1024th merged pull requests.
References
- GitHub Docs: Profile reference
- GitHub Docs: Manage visibility settings for private contributions and achievements
- GitHub Docs: Profile contributions reference
- GitHub Changelog: Achievements public beta
- Official achievement fragment corpus
- GitHub Achievement Index
- Achievement Guide Standard
Last verified
19 July 2026 — verified against GitHub’s live x4 Pull Shark detail fragment, including linked milestone history at 2, 16, 128, and 1,024 merged pull requests. Attribution and processing edge cases remain documented limitations.