New GitHub Profile Badges Beta
github.blog
github.blog
It seems like almost every tool or platform these days needs a friends feature, bragging badges or other form of social validation.
I’ve definitely contributed more PRs during Hacktoberfest to get a t-shirt. I’ve done Strava runs when I might have otherwise skipped a day and been excited to see a new achievement.
I was able to do a variety of "good first" things: readme updates, typo fixes, adding small features -- but it was hard to feel really _validated_ that my work was valuable, or that contributing to open-source was an impressive thing to do, because I (felt like I was) was surrounded by engineers, and nobody ever told me that OSS was "cool", until I met a company 3 years into college who valued OSS (more than just "wow, great job, you fixed a typo!")
Under this system, I get no badges. I appear as though I have nothing to show. Even though I have arguably done more and been responsible for more than many people with badges have. That's irritating.
Edit:
I actually can't think of any such site _without_ comment voting today. Really that's because virtually every social media site now has a one-click way of engaging with comments (notably excluding 4chan). The difference between sites is in whether sorting by score is lacking, available, or part of an inscrutable algorithm; and what other ranking methods are available.
I can't find a single result relevant to the history of voting or user moderation in any search engine. Was Slashdot the first? It and Fark lacked this at launch in 1997;
- Slashdot handpicked 400 users to be moderators in 1999-03[0], and began randomly assigning moderation duty some time between then and the addition of moderation reasons in 1999-05[1]. Metamoderation was added in 1999-09.[2]
- Fark only added comment voting, with separate 'smart' and 'funny' votes, in 2011,[3] making it the only social news site AFAIK without negative votes.
</rabbithole>
[0] https://news.slashdot.org/story/99/03/23/1058204/slashdot-mo...
[1] https://news.slashdot.org/story/99/05/24/1848220/slashdot-no...
[2] https://slashdot.org/story/99/09/07/155233/slashdots-meta-mo...
[3] https://www.fark.com/comments/blog256/New-feature-Favoriting...
*videogames
And the term for introducing in non-game areas game elements such as achievements is gamification.
It's smart.
This is WHY Microsoft bought Github. Software is eating the world and Github is where most of the eating happens. There are many career paths that require you to live on Twitter or LinkedIn or whatever. If Github pulls off the bigger play here it won't matter what Gitlab or Bitbucket or anyone else ever tries because you will HAVE to be on Github.
This is how a trillion dollar company gets its return on GH.
Given that Stack Overflow has shut down their (very popular) jobs board along with the relevant developer profiles [0], this seems like a great time for Github to try and grab a part of the pie.
[0] https://meta.stackoverflow.com/questions/415293/sunsetting-j...
Achievements is a way of distilling contributions down to the important questions that hiring managers have: just how senior is this person I'm interviewing anyway? If I hire this person to do cutting-edge work, are they the kind of person to interact with the community on pushing the state-of-the-art, or not?
Rather than looking at github from the perspective of hiring managers, look at it from the perspective of users. If the feature does not seem to serve them, it might not be a good one.
If github is a tool, then the words hiring manager probably shouldn't appear. I don't think of "what will my product person think?" when I use grep.
Also, didn't we do this when the award was tshirts for commits to open source projects where it unleashed a firestorm of junk edits to projects?
If SNR gets low enough, people will migrate. I know some people have left github for gitlab, and are having a whale of a time with their runners etc. Replacing junky old jenkins installs for in the fence CICD.
It sounds like your perspective is that users don't get any value out of social media?
Why do people post photos to Instagram? Why post updates to Facebook?
You can take photos for your own benefit (like writing code for some non-GitHub-related benefit, e.g. work) and also share them on social media for your own gratification. You can live life for the fun of it and also share it on social media for your own gratification. (leave aside that social media is net-toxic, it's still worth it to understand the motivations of those who engage with social media).
Don't want to engage with the social media aspects of GitHub that they're adding (because social media is net-toxic)? Fine. Disable the achievements. They (smartly) built in that disable switch. But don't presume that there isn't a large portion of GitHub's userbase that won't get value out of this.
Why? Everybody I've talked to who's considered alternatives and still uses GitHub for projects that don't have to be on GitHub does it because they're looking at it from the perspective of potential employers. (Or because they like GitHub's Projects feature enough, but those are rarer.)
What do you think happens after GitHub earns a reputation for alienating OSS project leaders by incentivizing low-quality contributions?
This is yet another short-sighted and stupid decision towards making GitHub into the next SourceForge.
To me, this strategy was the right one 5+ years ago and Microsoft is behind the trends.
I see this backfiring if they push it too hard.
We really shouldn't be encouraging this.
This "achievement" is not indicative of anything at all.
I set up build+test via GH actions and have GitHub run them on PR's. And make all changes through PR's.
This not only prevents "forgot to run tests" type accidents during regular development, it also helps me when I come back to a hobby project months later, and it lets me confidently do small changes (think version bumps) directly through GitHub's editor, which saves a bunch of time.
And when, against the odds, I actually do get a contribution, the infra is already there and it really cuts down my turnaround time to get it merged, bump the version and deploy the release.
Of course if a single direct push yields you the badge then I guess pretty much every solo dev gets it sooner or later. But that indirectly turns it back into a good badge, right? "Independent enough to have a life outside a standardized corporate process"?
I just don't think merging without review equates is an absolute negative depending on the situation, in this case no reviewers exist outside of myself and from my perspective this is how a lot projects start, someone just goes for it and starts committing! Yolo...
Also check issues for discussion
It's saddening that GH is turning more and more into a gamified social network (the new "for you" feed).
I'm over here with 80% of my commit history just being recipe markdown.
What Code Climate is doing- I would love to see GitHub badges around that. Give me a badge because I pair unit tests with React components, or because I wrote something in an elegant way. That would actually be cool/useful. It would require that GitHub hires good devs though haha! Good devs at a major tech company - that will NEVER happen.
I understand that it's not for everyone, but I also feel like people here tend to forget that GitHub is a social coding/collaboration platform as well. If you didn't like these features, why are your projects on GitHub then? Plenty of other git solutions.
I see some comments worried about this feature being abused or misused in regards to "bad contributions" however those contributions would either just be rejected, as they should, or accepted by the maintainers which means the badges worked to begin with, promoting more open-source collaboration.
Because it also works really well for solo projects or private projects.
I chose GitHub many years ago not because they were social but because they were free and accessible. The competitors at the time were sourceforge and Google code and neither of them were as easy to use or simple.
I use GitHub in spite of its dumb social features, not because of it.
This reminds me of the “if you don’t love guns, why do you live in America, gtfo” people are complicated and have multiple, sometimes conflicting, motivations.
But I'm not sure how good it is to work on such a project for a long time in terms of career growth. Telling your next potential employers your body of work at Github is a Badge CRUD sounds pretty underwhelming.
With that said, and I know GitHub is big and lots of people are working on lots of things, however I feel like whatever energy went into this could have possibly been spent on making the UI more responsive and less wonky. For instance, I still continue to run into issues when opening PR links from the Slack integration where it won't load the CI status correctly, I have to refresh the page every time.
I love GitHub, and I'm not someone who is trying to harsh anyone, and I think this is kind of cool for what it is, however there are many long standing UI / UX issues make this landing a little less exciting.
On one hand, I don't think there's anything particularly wrong with additional badges -- I thought the first two (the Mars Rover and "code vault" ones) were pretty interesting, and told an interesting story. On the other hand, these feel much more gamified: I don't know what "YOLO" or "Pull Shark" is supposed to mean to me when I see it on someone's profile. And this is coming from someone who really likes the other social aspects of GitHub: I like seeing people's commit timeline, pull histories, &c.
IMO, the failure here is not in concept, but in execution. Rewards and validation are nice; I'd like to see GitHub reach a bit higher with them.
What is the value of encouraging low quality contributions?
Very soon, you will be able to buy GitHub profiles with a lot of badges and followers I guess.
Plan and schedule issues with automated iteration cadences (great for recurring annual tasks)
Container Scanning available in all tiers (already very easy to add container scanning in enterprise, but now available for free everywhere, have to use a third party action in github)
Project-level Secure Files in open beta (missing from github)
Semgrep-based SAST (in addition to their existing SAST & DAST, something github lacks natively)
Approve deployments from the Environments page (GitHubs approval flows are enterprise only)
Improvements to Terraform registry
--
GitLab is already well beyond the feature set of GitHub, you should give it a look sometime.
Things that immediately jump out to me:
1. Security Dashboards
2. Kubernetes Integration (automated test environments)
3. SAST / DAST / OSS license checks / compliance frameworks
4. Feature Toggles using unleash (hosted by Gitlab)
5. More robust project planning, way beyond 'issues'.
6. Can read in results from unit testing / cypress without adding additional plugins
7. Can send alarms from your observability platform of choice to indicate release health
8. OpenFaaS support
I just did this.
On one hand, yes it's fun and brings entertainment to the platform.
On the other hand, I don't really want a badge showing I sometimes "YOLO" merging code like it's an achievement or something. It's not the achievement you think it is, even if it's a common meme for people new to the industry. It leaves a breadcrumb trail of bad practices that are sometimes out of necessity.