Slashie's Gamedev Adventures

how-many-days is a command-line tool that counts the distinct days of work recorded in a git history — not commits, not calendar span, but the number of separate days somebody actually committed something. Point it at a repository and it reports that number. To use it just run npx how-many-days in your repo.

New feature! added a --by parameter set that allows you to split the counts by year, month, week and author. Not just a single parameter, you can send several of them as needed to obtain a composite breakdown.

$ how-many-days --by year
584 days of work on master
  commits         3180
  first day       2014-03-10
  last day        2026-06-15
  calendar span   4481 days
  longest streak  13 days
  commits per day 5.4 avg
  authors         5
        days  commits  authors
  2014   166     1017        3  #######################
  2015   175     1077        1  ########################
  2016   139      619        3  ###################
  2017    76      335        1  ##########
  2018     2       10        1  #

This was triggered by my own need to measure the work put into multi-year projects, by myself. The outcome of this will likely affect how things are shown in both slashie.net and slashie’s keep.