Pair Extraordinaire achievement not unlocking despite valid co-authored merged PRs

[Dotoryman]

🏷️ Discussion Type

Question

💬 Feature/Topic Area

Profile

Body

What are you trying to do?

I'm trying to earn the Pair Extraordinaire achievement through legitimate co-authored commits that are included in merged pull requests.

I have tested the requirements multiple times with real GitHub users, including testing both directions of co-authorship.

What did you expect to happen?

I expected the Pair Extraordinaire achievement to appear on my GitHub profile after the qualifying co-authored pull requests were merged into the default branch.

What happened instead?

The achievement has still not appeared on my profile, even though GitHub itself correctly recognizes the co-authorship.

For example, I tested this with another GitHub user in both directions:

Test 1 — I am the co-author

Repository: seojiwon99/dotory
Pull Request: #85

• Primary author: seojiwon99
• Co-author: Dotoryman (me)
• The commit contains a valid Co-authored-by trailer using the email associated with my GitHub account.
• GitHub correctly displays both seojiwon99 and Dotoryman as authors.
• The pull request was merged into the repository's default branch (master).

Test 2 — I am the primary author

Repository: seojiwon99/dotory
Pull Request: #86

• Primary author: Dotoryman (me)
• Co-author: seojiwon99
• GitHub correctly recognizes both accounts as authors.
• The pull request was also merged into the default branch.

I have also completed additional co-authored merged pull requests in another public repository with multiple real collaborators.

Despite this, Pair Extraordinaire has still not unlocked.

My GitHub profile is Dotoryman.

Since GitHub correctly recognizes the co-authorship on the commits themselves, could this be related to an Achievement/profile synchronization or indexing issue?

I have also noticed other recent Community reports about GitHub Achievements not appearing as expected, so I would like to know whether Pair Extraordinaire is currently affected by a known issue.

Any links/screenshots?

Profile: https://github.com/Dotoryman

Repository: https://github.com/seojiwon99/dotory

PR #85: seojiwon99/dotory#85

PR #86: seojiwon99/dotory#86

I can also provide commit SHAs or additional screenshots if needed.

[TongyiDai]

I verified both examples through GitHub's APIs. The repository is public and not a fork, master is the default branch, and PRs #85 and #86 were merged into it on September 11. GitHub GraphQL resolves two account-linked authors on each commit:

• PR #85 / commit cbeb5bae...: seojiwon99 + Dotoryman
• PR #86 / commit ba04ec8e...: Dotoryman + seojiwon99

Each commit is also associated with the expected merged PR. So the observable repository-side prerequisites are present; this is not explained by an unrecognized trailer, wrong base branch, fork, or missing PR association.

GitHub Community currently has an acknowledged incident covering achievement badges not appearing or profile data rendering incorrectly: https://github.com/orgs/community/discussions/203416. I would add your account and these two PR/commit pairs to that incident rather than creating more test commits. More synthetic tests will not distinguish eligibility from failed achievement indexing.

Only GitHub can confirm its private qualification rules or reprocess an achievement record, but your two examples are already a clean reproduction set for that investigation.