I need a blog post to be written on why judging developers or technical people based on their Github Profiles is hard. The following outlines the points I want to cover. Of course they will require more research, screenshots and the points to be assembled well.
---- Outline ----
People usually ask for a github profile as a part of the resume. Let me share with you, why I think you should not judge someone on their github profile.
The commit graph
I have been developing for 10yrs. I have been using github for about 5 yrs. If you are looking at my personal projects, you will find a lot of commits, but spaced out at very long intervals of time. The no of commits don't really give an idea of the quality of my code. Sometimes the amount of Code I have deleted is more important than my the number of lines I have written.
If a company uses Github, the majority of a person's work is going to be in private repository. Again, the commit graph is only a small indicator of his technical abilities.
Bugs on Open Source projects. Let me just start by saying that the barrier here is really high. People who do PRs against bugs are at the mercy of the authors time and opinion. An author could be very opinionated and can refuse to merge even if the solution works. Resolving a bug, also happens when the developers run into a problem themselves. When developers run into a problem, they mostly find a replacement library. Resolving the bugs doesn't really give them an incentive unless they have made a heavy investment in the library previously.
Forking a Repo is really just copying it and modifying a few pieces. You can't end up with the credit of customization. It shows a lot of Code, but figuring out a single persons contribution is really hard.
Gists and Documentation
Gists and documentation are really the two small pieces that will really give you an idea. In fact, gists can be really well documented too. Small independent pieces of Code that you can run anywhere.