Paul Barry

A rake task for tracking your time with git

July 7, 2009

Are you using Ruby on Rails? Are you using Git? Do you have a need to track how long you spend on things? Then I have just the thing for you.

I threw together a quick rake task that gets all of your commits in a git repo and parses out the times and commit message from them. Then it formats them with the time and also the time interval between them. You can get the rake task to track your time from this gist.

The output will look something like this:

Fri, Jul 07 10:55AM  20m 49s  Added toolbar for controllers using temp...
Fri, Jul 07 10:34AM  21h 52m  Added support for using page templates i...
Thu, Jul 07 12:42PM  37m 57s  LH#77, fixed issue with tests failing on...
Thu, Jul 07 12:04PM  12m 18s  LH#67, added a limit option to the rende...
Thu, Jul 07 11:52AM  17m 30s  Removed debug statement                 ...
Thu, Jul 07 11:34AM  19h 52m  LH#66, added :path option to render menu...
Wed, Jul 07 03:41PM           Added DSL for modifying portlet behavior...
Tue, Jun 06 02:05PM  18h 44m  LH#119, multiple HTML fields on one bloc...
Mon, Jun 06 07:20PM   6h 21m  Converted docs to textile               ...
Mon, Jun 06 12:58PM           Fix for LH#118, create directories in ge...
Sat, Jun 06 10:22PM           Added support for other template handler...
Fri, Jun 06 04:49PM   0m 58s  bump build                              ...
Fri, Jun 06 04:48PM  23m 11s  Fix LH#106: Section not correctly loadin...
Fri, Jun 06 04:25PM  34m 25s  Fix for LH#107, images were not showing ...
Fri, Jun 06 03:51PM   9m 48s  Fix for LH#110, can't view usages of a p...
Fri, Jun 06 03:41PM  11m 12s  Fix for LH#113, check to see if there is...
Fri, Jun 06 03:30PM   2m 52s  Fixed LH#114, documentation typo        ...
Fri, Jun 06 03:27PM   0m 38s  bump build number                       ...
Fri, Jun 06 03:26PM   5h 38m  Fix for LH#98, tags not getting updated ...
Fri, Jun 06 09:48AM  33m 14s  Fixed LH#105, deleted portlets showing u...

It doesn’t actually truncate the commit messages, I just did that here to make each one fit on a line. If the time interval is over 24 hours, it doesn’t bother printing the interval, because you probably didn’t actually work on that one commit for 37 hours straight. I’ve been thinking if you really want to track time this way then each time you sit down to start hacking on a project, you just make a minor change to the .gitignore or something and then commit it with a message like “started hacking on foo”, so then when you commit your first chunk of actual work, you will know how long you spend on that.

Posted in Technology | Topics Git, Ruby, Rake | 4 Comments

Comments

1.

I threw together a quick shell script to track the start of work.

http://gist.github.com/142125

Just run script/work (or whatever you want to call it) when you sit down to start.

# Posted By Jonathan on Tuesday, July 7 2009 at 11:01 AM

2.

I know this isn't the greatest way to work, but I sometimes find myself with a backlog of changes waiting to be committed, and will stage several logical chunks into multiple commits within a span of a few minutes. I've thought about automating time tracking with something like this, but in the end while I'm in flow I just don't want to be bothered worrying about time.

I do think that storing your time tracking data within the git repo is a great idea, I just haven't thought of the perfect solution for my workflow yet.

# Posted By Lar Van Der Jagt on Wednesday, July 8 2009 at 2:02 AM

Comments Disabled