It’s not possible to measure developer productivity, but “developer hertz” is still tied to commit count so not ideal. This is a problem I think is important enough to deserve a metric to measure the rate at which a repo evolves (emphasis on updating legacy code). When GitClear started building Line Impact 5 years ago (free as of 6 months ago) our hope was that someday devs would pick a metric that’s better than commit count, and one that prioritizes dev-control of long term data (as GC does). If GitClear sounds familiar prob because we also support open source projects like libinput, but eventually we hope to be known as the dev-centric metric provider
