Github Streak

Github Streak

17 Jan 2015

tags: github

I am a pretty lazy person by nature. I like learning new things, but I have a problem following through, which is why I tend to read more articles than I read books.

So, this year, I only made one resolution because I know that I am way too lazy to keep up with any list that that contains more than one items.

No.1 Goal: commit everyday (to Github)

My streak on Github is now 15 days in a row (whoohoo), most if not all were commits to the foreign language learning project Chelsea and I are working on, which is the only way I can really learn webdev.

While I was trying out this goal, I learned a couple things about how Github keeps track of "streak" for its user.

How Github Counts Streak

First an formost, it really only counts your commits as streaks as long as you don't delete the projects you made the commits with. If you kept a long streak going, and created a project of which you worked on for 3 days and then went on to working on other projects, then you one day decided to delete the project, Github would count your streak from the point after you worked on the project you deleted, which means that you lost all the streak days you have accumulated prior to the day you worked on the deleted project.

Branching

If you created a branch and did some work with it, until the branch is merged with the master, your work will not be counted. So, when I created a branch to test out some user stuff for the lang project I was working, my streak was zero until I merged the branch to the master and my streak returned to what it was plus the days I worked in the branch.

There are still probably a lot of rules that I haven't discover, but these are the ones that I have discovered.

There are days when I am lazy, and my only commit would be "fix typo", but I hope that by developing a habit of coding regularly, I can familiarize myself with various tools that can help me become a better creator. *fingers crossed*