I agree. I don't think my clients would appreciate adding time tags to each commit. It's nonessential information which is better placed in a different system

I agree. I don't think my clients would appreciate adding time tags to each commit. It's nonessential information which is better placed in a different system, referencing the commit if needed. Once the invoice has been taken care of, the time tags become meaningless while the rest of the information is still very important. I would rather my history always stay clean. Another issue is that when you start down this road, where does it end? You start out with time, and then you might start thinking about what other nonessential information you could put in there. Each commit might then start looking like a config file for your swiss army approach to using Git as a project management tool. I think there still could be a use for this. It could still import the commits into a time tracking system for convenience. Props to the developer though. Everyone is free to make their own decision and some developers will love this. Edit: I just saw the reply which suggested possibly using git notes. I didn't even know about git notes. I will check that out, thanks!