As the resident "I want my commits to be beautiful" purist around here, I have to say that I really, really dislike this idea. Commits are rarely exactly bound to a specific billable item on an invoice.<p>Implementing a feature could and often does cause mutliple commits.<p>A system like this either encourages to mush everything together into one commit (bad) or it creates basically empty or non-related commits after implementing the feature so it appears on the invoice.<p>But this is just me. I see how this could be useful for people who are not such purists as I am. On the other hand: In my SVN times, I would have used a service like this in a heartbeat. Even in my early git days.<p>But after learning about optimizing commits and about the beauty of a clean history, I now changed my mind about this. So ask yourself: Is there any chance you might shift in your thinking about the commit history? If yes, do you really want to have commits in your history that you might at one day consider to be really bad ones?
This is awesome, and came at just the right time for me!<p>Last February, in my last semester of college, I heard about an iPad contracting job. I had never done any freelance work before, so I thought it would be a good opportunity to see what it was like. I gave the client a whole-project quote based on some conservative time estimates and an hourly rate a little below the market.<p>After that I didn't really track hours since they were paying per feature milestone, so when the project was over I had no idea how much time I had actually spent on it. I had planned to write a utility to estimate the time from my Git commits. You beat me to it! (Turns out I'm faster than I thought. :-))<p>I just finished writing my own time tracking tool, but I may use this instead for projects that can be represented entirely by their git repository.<p>Some comments:<p>- I have a <i>lot</i> of repositories, most of them small personal projects or other people's open source projects. Can you let me only import a couple, maybe preferring private and recent repositories?<p>- The design is very nice<p>- Can you separate the time estimation from the cost calculation? I'm sure a lot of people are interested in that functionality by itself.<p>- If I'm going to back-fill estimates, I want to see the diff, but the links to the commit diffs are on the page before you can enter the estimates. Add links to the page where you can enter your own estimates!
Nice work. Simple idea and well executed.<p>Two quick things came to mind.<p>An option to only select commits with entered times would be handy rather than having to deselect the estimates and non value commits (maybe this is implemented but I didn't create a commit with a time value).<p>Think someone else mentioned this, but the ability to override or add time to estimated and/or non value commits.