What's up with Gitminder?

I’ve been watching it for some time and there are a couple of quirks that bother me:

  • It does seem to be taking the initial commit as two of them. I have wild guess it could be related to initiating GitHub repo with initial files through the interface (I do that) but it’s still one commit. I can’t test it right now.

  • I did a merge to master today. Noticed a critical issue. Amended the merge commit and force pushed it. I know it’s bad but people do that more than they care to admit. Gitminder counted this one commit as 5 (there were 4 commits in the branch). I’m not sure whether it occured on merge itself or after the force update, but I seem to remember a simple merge being OK before. GitHub counts two contributions in that repo today i.e. pre-force commit and it’s variant after forced update - so Github kinda looked through all my playing with force updates and counted the right amount of commits somehow.

  • How hard it is making contributions goal? Especially as far as GitHub already ensures it’s counted correctly.

1 Like