← Git Timesheet

How to estimate hours worked from git commits

Paste your history into Git Timesheet to get hours per day and a client-ready summary. This is the method behind the number, and where it is weak.

Does this upload my git history?

No. The page parses the text you paste in your own browser and sends nothing anywhere. The CLI reads your local repository and makes no network call.

How are hours estimated from commits?

Commits less than the idle gap apart (default 2 hours) form one working session. A session counts its span plus lead time (default 30 minutes) for the work before the first commit. Each contributor is estimated separately.

Is the estimate accurate enough to invoice?

It is a defensible starting point, not a time record. Meetings, research, review and debugging without commits are not captured, so check the total against your own notes before you send it.

Which git log format does it need?

git log --pretty=format:'%H|%an|%aI|%s'. The copy button gives you the exact command.

How should I present estimated hours to a client?

Say they are estimated from commit activity, add the time you know git cannot see (calls, planning, review), and attach the day-by-day summary so each line of work is visible. Agree the method before the first invoice, not after.