Who likes to collaborate to unlock Pair Extraordinaire badge ? #211668
Discussion TypeProduct Feedback Discussion ContentHi, 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 |
Replies: 5 comments 3 replies
|
💬 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 ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
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. ⭐ |
|
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:
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. |
|
Hi, thanks for the suggestions. 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 |
|
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. :) |
|
Done — your credit is in: kittimzhe/insightloom PR #4 (merged just now, Nov 1 14:22 UTC, zero reviews). The commit carries 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. |
|
Done — your credit is in: kittimzhe/insightloom PR #4 (merged just now, Nov 1 14:22 UTC, zero reviews). The commit carries 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. |
|
Done — your credit is in: kittimzhe/insightloom PR #4 (merged just now, Nov 1 14:22 UTC, zero reviews). The commit carries 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. |
|
noted with thanks, have marked your reply as answered. Look forward to the Pair Extraordinaire badge and more collaborations with you in future ya :) |
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 sid…