Why were Heart on Your Sleeve and Open Sourcerer achievements briefly re-enabled and then removed again? #191031
Replies: 3 comments
-
What Actually Happened - and What We KnowWhy They Briefly ReappearedGitHub's official explanation is that the temporary re-instatement was done in error — both badges were part of an experimental rollout and weren't meant to be re-enabled broadly. Once the mistake was identified, they were removed again. This wasn't a deliberate preview or announcement; it was a side effect of a separate fix (GitHub was simultaneously resolving an unrelated bug where all achievements had disappeared from profiles). Why They've Been in "Experimental" Status for So LongThere's no official public statement explaining the delay, but based on what's surfaced across community discussions, a few factors are likely in play: 1. Criteria overlap with existing badges 2. Known planned criteria, but no release gate 3. No public timeline has ever been shared Is There Hope for a Release?Realistically: unclear, but not dead. The fact that they keep surfacing in accidental rollouts suggests the backend infrastructure exists and is functional. The most likely scenarios are:
What You Can Do Right NowSince there's no release timeline, the best move is to make your open source work visible through other means that are live today:
The work you're doing is already verifiable. The badge is just a shortcut - and the shortcut isn't available yet. ** GitHub has confirmed it was an error, the criteria are internally decided, but there is no public release date and no explanation for the delay. The most honest answer the community can give is: we don't know when or if these will launch, and GitHub has chosen not to say either. |
Beta Was this translation helpful? Give feedback.
-
|
ok so basically github themselves came out and said it was a mistake lol those two achievements (heart on your sleeve + open sourcerer) were part of an experimental rollout that wasnt supposed to go live for everyone - someone at github accidentally re-enabled them broadly and a bunch of ppl got them for like a few hours before they caught the mistake and pulled them back so if u woke up one day and saw them on ur profile and then they just vanished - ur not going crazy, that literally happened to a ton of ppl 😭 theyre still in testing/beta rn and github hasnt announced when (or if) theyll fully release them to everyone. keep an eye on the github blog i guess, thats prob where theyll announce it when its actually ready |
Beta Was this translation helpful? Give feedback.
-
|
Hey guys, quick question – has anyone here seen this site before: (https://real-world.wuaze.com)? The algorithm threw it my way while I was researching this topic. It looks legit and super useful, but I prefer to ask around before trusting a new platform. Anyone tried it out? |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
🏷️ Discussion Type
Question
💬 Feature/Topic Area
Profile
Body
Hi GitHub team and community,
I noticed that the Heart on Your Sleeve and Open Sourcerer achievements appeared briefly on profiles recently, and then were removed again. A maintainer clarified that this was done in error — they were part of an experimental rollout and weren't meant to be re-enabled broadly.
I completely understand that mistakes happen, and I appreciate the transparency. But I'd love to understand a bit more:
I wanted to share a personal perspective too — I'm a third-year Electrical Engineering student from a Tier III college in India, actively contributing to open source as part of my #100DaysOfIoT challenge. For someone like me, who doesn't have the brand name of a top-tier institution on their resume, achievements like the Open Sourcerer badge carry real weight. They're a visible, verifiable signal to recruiters and researchers that "this person actually contributes to the community" — not just builds private projects.
When it briefly appeared on my profile, it genuinely felt like recognition for months of work. And I know I'm not alone in feeling this way — a lot of developers from non-elite backgrounds rely on these small but meaningful signals.
I'm not asking for a timeline or a promise — just some clarity on the direction. Even a "we're still figuring it out" would be appreciated more than silence.
Thanks for everything you do for the developer community. 🙏
Beta Was this translation helpful? Give feedback.
All reactions