[sftwds]

The commits per hour statistic looks to be how many commits occurred in each hour of the day: https://github.com/arzzen/git-quick-stats/blob/master/git-qu.... For CI/CD requirements you really want to measure the time difference between every commit and the previous commit. That way you can say that if your CI/CD processes take less than X amount of time, they will finish before the next commit Y% of the time.

[paulddraper]

Not necessarily.

At any reasonable size, you have to be able to run builds and tests for features in parallel. And at that point, throughput and scale throughout the day is rather important.