Pair Extraordinaire not counting co-authored merged PRs since Oct 8

[marcos-grocha]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Profile

Body

What I expected
Co-authored commits in merged pull requests should count toward the Pair Extraordinaire achievement. I should be at the x3 tier (24+ PRs).

What happened
My account (marcos-grocha) is stuck at x2. On 2026-10-08 I merged 17 PRs in the public repository marcos-grocha/devmobile-me1 (#1 to #17). Every one has commits with Co-authored-by trailers linked to other GitHub accounts, and the co-authors show up on the commits in the UI and the API. None of these PRs seem to have been counted, for me or for my co-authors: one of them co-authored all 17 and still has no Pair Extraordinaire at all.

On 2026-10-13 I merged another co-authored PR (marcos-grocha/sj-26#24). It wasn't counted either, so this doesn't look like a delay.

What I checked

• The repo is public, and the PRs were merged normally into the default branch with merge commits.
• The co-author emails are linked to the accounts; GitHub lists both authors on the commits.
• It has been 5+ days since the merges.

Is achievement processing currently delayed or broken? Has anyone else seen this recently?

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[kittimzhe]

Live-checked your claims just now — they all hold, and the answer to your question is yes: achievement processing is currently broken platform-wide, not just slow for you.

What I verified:

• All 17 PRs in devmobile-me1 show merged: true (e.g. Feature Request: Checklist button in toolbar #17 at 2026-10-08T19:55Z) — properly merged via GitHub, not just pushed merge commits.
• The feature commits carry Co-authored-by: trailers, and the repo is public.
• Your profile shows Pair Extraordinaire (x2) alongside YOLO, Pull Shark and Quickdraw — so pre-Oct-8 counting worked normally.

Why nothing since Oct 8 has counted: this is the achievement backfill incident. GitHub staff confirmed on Sep 23 (marked answer in #208263) that internal teams are investigating achievement-granting delays of "several days" with no timeline; the aggregation thread #203416 is at 115+ comments with users waiting three weeks and counting — my own achievements triggered Sep 18 and Sep 25 are still pending today. Your Oct 8 batch sits squarely in that window, and your co-author's missing first Pair Extraordinaire is the same "first badge stuck in the pipeline" pattern seen across that thread.

One separate check: marcos-grocha/sj-26#24 returns 404 to the public API — if that repository is private, its PRs are correctly excluded (achievements only count public repositories), so don't use it as a signal either way.

What to do: add both usernames (yours and the 17-PR co-author) and the merge dates to #203416. Your tier math holds — 17 qualifying merges on top of an x2 count crosses your stated 24-PR x3 threshold — so once the pipeline recovers, the jump should land. If the incident is declared fixed and these still don't count, that's the moment for a support ticket with the PR list.