Who likes to collaborate to unlock Pair Extraordinaire badge ?

[Githubuser1708]

Discussion Type

Product Feedback

Discussion Content

Hi,

I am looking for a collaborator who is experienced in unlocking the Pair Extraordinaire badge in prior collaborations because I tried several times with another friend account but did not manage to unlock the badge, do not know why...

Is anyone who has done this successfully before can help to collaborate together ?

Once completed, I will marked your reply as answered and closed this. 🙏

Thanks much

[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]

Happy to pair — but first, the reason attempts like yours fail is almost always one of three fixable mistakes, so check these against what you did with your friend:

1. The Co-authored-by: trailer must be inside the commit message body, not the PR description. GitHub's UI suggestion only appears when the commit already carries it. The format that counts: Co-authored-by: Name <ID+username@users.noreply.github.com> as the last line of the commit message.
2. The repo must be public — co-authored merges in private repos don't count.
3. The PR must be merged (not just closed), and both the author account and the co-author account get credit from the same merge.

My offer: I can merge a small PR in one of my public repos with your co-author trailer in the commit message — that single merge qualifies both of us. If you want a second data point you can reciprocate in one of yours. One expectation to set: achievement issuance is lagging platform-wide right now (the #203416 incident — my own pending badges have taken weeks), so the badge may not appear instantly even when done perfectly.

If that works for you, reply here and I'll set it up.

[Githubuser1708]

Hi, thanks for the suggestions.
can clarify further the below points.

The Co-authored-by: trailer must be inside the commit message body, not the PR description. GitHub's UI suggestion only appears when the commit already carries it. The format that counts: Co-authored-by: Name ID+username@users.noreply.github.com as the last line of the commit message.

=> i have encountered that there are a few stages from doing a PR e.g during< commit > stage, after this stage, there is and etc. for each stage, there is a Description section window for any comments. Does the Co-authored-by: Name ID+username@users.noreply.github.com needs to be added at each description section ? for the email , can use the email that is registered in github (other than the xxx@users.noreply.github.com)? thanks

[Githubuser1708]

sure, thanks for the offer, yes would be keen with the collaboration. would close this and mark as answer once the badge is released for both of us . thanks much. :)

[Githubuser1708]

hi.. just check my profile .. seems have not unlocked the pair badge....

[kittimzhe]

Done — your credit is in: kittimzhe/insightloom PR #4 (merged just now, Nov 1 14:22 UTC, zero reviews). The commit carries Co-authored-by: Githubuser1708 <141693329+Githubuser1708@users.noreply.github.com> in the commit message body, in a public repo, merged — every documented condition met for both of us:
https://github.com/kittimzhe/insightloom/pull/4/files

You can verify the credit renders on the commit page (your avatar should appear as co-author of a6e3065).

On timing: given the current issuance lag (#203416 incident), expect days rather than hours — measured window for recent triggers has been roughly 6–9 days. Fingers crossed it's shorter for both of us; I'll watch for it on my side too.

[kittimzhe]

Done — your credit is in: kittimzhe/insightloom PR #4 (merged just now, Nov 1 14:22 UTC, zero reviews). The commit carries Co-authored-by: Githubuser1708 <141693329+Githubuser1708@users.noreply.github.com> in the commit message body, in a public repo, merged — every documented condition met for both of us:
https://github.com/kittimzhe/insightloom/pull/4/files

You can verify the credit renders on the commit page (your avatar should appear as co-author of a6e3065).

On timing: given the current issuance lag (#203416 incident), expect days rather than hours — measured window for recent triggers has been roughly 6–9 days. Fingers crossed it's shorter for both of us; I'll watch for it on my side too.

[kittimzhe]

Done — your credit is in: kittimzhe/insightloom PR #4 (merged just now, Nov 1 14:22 UTC, zero reviews). The commit carries Co-authored-by: Githubuser1708 <141693329+Githubuser1708@users.noreply.github.com> in the commit message body, in a public repo, merged — every documented condition met for both of us:
https://github.com/kittimzhe/insightloom/pull/4/files

You can verify the credit renders on the commit page (your avatar should appear as co-author of a6e3065).

On timing: given the current issuance lag (#203416 incident), expect days rather than hours — measured window for recent triggers has been roughly 6–9 days. Fingers crossed it's shorter for both of us; I'll watch for it on my side too.

[Githubuser1708]

noted with thanks, have marked your reply as answered. Look forward to the Pair Extraordinaire badge and more collaborations with you in future ya :)

[Githubuser1708]

Hi, wondering how long will the unlocking take ?

[kittimzhe]

Window-closing update, and a proposal for round two: PR #4 merged 9 days ago (Nov 1, 14:22 UTC) — past the 6–9 day issuance window I've measured for this incident — and Pair Extraordinaire hasn't appeared for either of us. I've been watching both profiles.

That result is actually informative: your account's achievement pipeline demonstrably works (your YOLO, Pull Shark and Quickdraw all issued), yet the same single merge that should credit us both produced nothing on either side — which points to the achievement event for that merge being lost upstream rather than either account being ignored.

So, if you're still willing: round two, reversed direction — this time you author and merge a small PR in your public repo, with my trailer in the commit message body:

Co-authored-by: kittimzhe <67472034+kittimzhe@users.noreply.github.com>

Same rules as round one (public repo, merged PR, trailer inside the commit message — not the PR description). Different repo, different author role, fresh event — if this one also vanishes for both of us, that's two independent event losses on record, which is exactly the kind of data point the incident thread (#203416) can use.

No pressure and no rush — say the word and it's a two-minute job on your side. I'll keep watching both profiles either way.