GitHub Pull Shark achievement guide

GitHub Pull Shark achievement

Pull Shark recognises pull requests that are successfully merged. This guide separates confirmed behaviour from community-reported tier thresholds.

What counts

A qualifying event should involve a real pull request that is merged into a repository. The contribution should contain a substantive change and remain attributable to the account seeking the achievement.

What does not belong in a responsible workflow

Empty or deliberately meaningless pull requests
Whitespace-only changes created solely to inflate activity
Misleading authorship or impersonation
Automated spam across unrelated repositories
Changes that breach a project’s contribution rules

Community-reported tiers

Tier	Reported merged PR threshold	Evidence status
Base	2	Strong community evidence
Bronze	16	Strong community evidence
Silver	128	Repeated community verification
Gold	1,024	Community-reported; not officially published

GitHub does not maintain a public official table for these tier thresholds. Treat them as community findings, not contractual guarantees.

Award delays

The badge may not update immediately after the qualifying merge. Profile processing, caching, and delayed achievement evaluation can all affect display timing. Avoid creating duplicate activity simply because the badge has not appeared yet.

Verification checklist

Confirm the pull request is merged rather than merely closed.
Confirm the PR author is the intended GitHub account.
Confirm the repository and activity are visible enough for later review.
Record the PR URL and merge timestamp.
Allow time for GitHub profile processing.
Recheck the profile before repeating any action.

Evidence status

Qualifying merged pull requests: Verified
Public tier table: Community-reported
Immediate badge delivery: Not guaranteed

Last verified

19 July 2026 — reviewed qualifying merged-pull-request behaviour, community-reported tier thresholds, award delays, and responsible participation guidance.