Skip to main content

Github is weird

So I'm coding all the time.  As a result, I find it somewhat hillarious that my github stats don't show it, mostly because I do a lot of my coding on private repositories not on Github.  In fact, as of late, I'm thrilled to be using my own GoGS server.  It runs great on one of my raspberry pis.

I've been coding a lot of javascript lately, so this post will be heavy in js terminology.  Don't mind that.  The sum of it is in the title and the screenshots.

What I actually did


Last night (this morning?) I forked a repository of an npm package I'm using in one of my projects.  I needed some new features added to it to make it work with the project, so I coded them.  The work spreads across 4 commits.



It wasn't much, and the commit to fix the tests didn't work because the original author wrote tests that assumed a specific timezone, so this wasn't yet pull request material.  To keep it simple, I put the commits on the master branch and simply point my project at my fork instead of the released versions of the project.

Later, after some sleep, I started researching base for my fork only to realize that the author hasn't even looked at pull requests since July of 2015.  So I looked at some other forks, and considered basing my potential pull request off of a more recent version.  Instead of just doing that and abandoning what is definitely the basis for the project on npm, as a courtesy to the author I posted an issue that the project appears to be dead and asked if we should redirect to a more active fork.



So, naturally, I expected Github to track my activity and show it in my contributions page.

What Github says I did




I noticed a few months back that github doesn't put anything on your contributions page if you are working on a branch that isn't "master" which must be annoying for people who don't use master as their main branch, but I can understand it and it results in "eventual" consistency with contributions showing up when your branch is merged into master.  But that seems silly.

What's worse, I noticed when I left my last job, that when you leave a team, your contributions to that team's private repositories no longer show up on Github either, but I guess I get that too...to the same extent.

As of a few weeks ago, I noticed that issues showed up as contributions on this display.  I can understand that issues are important, but to track them while not tracking actual commits....whatever I guess.

All of that helps it make more sense when you see that, even though my contributions are to a public repository on the master branch, they don't show up because the repository's a fork...But then I realized something extremely unpleasant.

That's not just wrong, it's detrimental


Leave aside the fact that this encourages people to spam meaningless issues onto every repository they can find.

I'd like to remind you instead that: I'm using the forked repo in production.  That means that the information that github is showing is actually the opposite of what contributions I've made to software development today.

I don't know what to say.  Maybe I'm using github wrong.  Let me know if you think so.  Otherwise, feel free to share your own github stories.  What's weird about github to you?.

Comments

Popular posts from this blog

How to identify a skilled programmer during an interview

How does one identify a skilled programmer?  No company that has interviewed me could tell the difference between myself and other programmers they'd interview.  The interview process is truly a game of luck in this industry--on both sides.  Both the programmer and the company are basing their actions entirely on luck.

Companies have come up with numerous methods to attempt to discern a good programmer from a bad one.  The best tricks they have include a series of math problems, algorithms, problem solving technique tests, and even obscure programming questions, some without definitive answers.  As an example: Is there an authoritative source of information on the core principles that define object oriented programming?  I've heard everywhere from 3 to 7.  In a field of research about a synthetic concept, an authoritative answer is almost impossible to obtain.

Programmers were then forced to study to the interview.  Careercup is one of my favorite sites for this.  This almost …

Dependency Injection - You're doing it wrong!

So I have worked at a lot of places and seen a lot of different styles of programming.  Early on in my career, I became acquainted with the concept of dependency injection.  It was a hard topic to grasp, but I have learned understand it deeply.  Now, when I step into a new application that uses it, I can very quickly see the flaws in the implementation, and there's a common one I want to talk about today: global singletons.  But we'll get to that in a minute.

What is Dependency Injection?
Dependency Injection is exactly what it sounds like.  You use it to inject your dependencies. The unique part about Dependency Injection though, is that you can do this at runtime.  Now this sounds fancier than it is.  By inject we don't mean they're downloaded for you.  You still have to have all of the parts installed where you want to run your app.

Dependency Injection is somewhat of a complicated topic to a newbie.  Let's start with defining the word dependency here.  Specific…

Managing Programmers

Working with other programmers is tricky.  That said, it's nothing compared to the job of managing programmers.  One of my favorite quotes about Perl is that (paraphrased) "a Perl developer is like a rockstar.  Now imaging having a bunch of rockstars in one room together and you will understand why you don't want an entire team of Perl developers."  It's not about Perl here though. What's important to understand is that any developer worth his salt is going to be like a rockstar.  And yes, there are a lot of professional developers out there who aren't worth their salt, but that's for another post another day.  Rockstar may not be the right term here, but think of it this way.  These guys are smart.  They may not be geniuses, but there's going to be things that they know that you don't and probably never will.

I've seen it more than once and it's not going to make some Product Managers happy, but I'm going to state a fact, an eleph…