YOLO Achievement Eligibility: Does a Merged PR Need a Bypassed Review Request? #213303
Unanswered
petersisay
asked this question in
Other Feature Feedback, Questions, & Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
🏷️ Discussion Type
Question
💬 Feature/Topic Area
Profile
Body
Hello GitHub Community,
I'm trying to understand the exact conditions required to earn the YOLO achievement on GitHub.
My account is @petersisay, and I have already enabled achievement visibility on my profile.
My profile currently displays Quickdraw and Pull Shark, but YOLO has not appeared.
I recently merged two pull requests in my public repository:
Repository: https://github.com/petersisay/lehulu
PR #1: petersisay/lehulu#1
769a846eff5f53197aee90b97f9b29445ae33666PR #2: petersisay/lehulu#2
f6c973f84f659b672a9a06185ed1d728252947d0I also contacted GitHub Support under ticket #5014792. The automated response directed me to Community Discussions and closed the ticket, so I am asking the community for clarification.
My questions
review_requestedevent followed by merging before the reviewer submits a review?I understand that GitHub's internal achievement evaluator may not be publicly documented. I'm not claiming that any particular theory is confirmed; I would appreciate real experiences, official documentation, or reliable technical explanations.
Thank you for helping clarify this.
All reactions