Joined October 2012
·
Achievements
56 Karma
464 Total ProTip Views

Walrus
The walrus is no stranger to variety. Use at least 4 different languages throughout all your repos

Mongoose 3
Have at least three original repos where Ruby is the dominant language

Mongoose
Have at least one original repo where Ruby is the dominant language

Github Gameoff Participant
Participated in the Github Gameoff 2012 building a game based on git concepts of forking, branching, etc

Charity
Fork and commit to someone's open source project in need
To be honest, I think this is more of a behavior observed among people who already have had experience with Central / Single Repository Version Control Systems like Subversion - they tend to carry this behavior to git. People like me who are still learning the ins and outs of git, commit, branch, merge on a regular basis - its fun and it's a practice in itself. Since I have never experienced other version control managements, I do not hesitate or exercise caution with my commits and branches. So, its simple - just erase the knowledge of other VCMs before starting on git.