News for hackers. Stuff that matters.
Re:Commit to Keep Coding – GitHub + Beeminder by mappum on Friday February 22, 2013 @03:41PM (#5266634)
I don't think counting commits is a good metric, because I know if it were me, I would start splitting my commits up into trivial changes in order to meet the count ("added comment", "added line break", etc).

It supports going by issues, which is better, but how about counting additions/deletions?

Re:Commit to Keep Coding – GitHub + Beeminder by dreeves on Friday February 22, 2013 @03:51PM (#5266701)
Ooh, yes, GitHub's impact metric. We should add that.

I think minding commits isn't as bad as it could be theoretically though. I feel like pride is sufficient deterrent not to do pointless commits. And general pressure for more fine-grained commits is probably valuable.

Re:Commit to Keep Coding – GitHub + Beeminder by mappum on Friday February 22, 2013 @04:03PM (#5266782)
Well, the repo I'm thinking about using this on is private, so I have no pride and no shame.

Wait, I guess this doesn't support private repos.

Re:Commit to Keep Coding – GitHub + Beeminder by dreeves on Friday February 22, 2013 @04:07PM (#5266810)
Oh, Gitminder does let you beemind private repos, as long as the github account you oauth with has access to it.
Re:Commit to Keep Coding – GitHub + Beeminder by bsoule on Friday February 22, 2013 @04:09PM (#5266832)
We've got an integration with Rescuetime as well so that you can mind productive or unproductive time. If weaseling on commits is an issue you could also just increase the number of commits you're committing to. Arms race between current you and future you!