7 ms·
The more interesting question with git statistics is what they are actually useful for. Tools like this seem to be guided by which data is available and easy to
by qznc 8y ago
The more interesting question with git statistics is what they are actually useful for. Tools like this seem to be guided by which data is available and easy to extract. What is commits per hour useful for?
Sometimes these metrics are useful. For example, the top committers are interesting, because it instantly gives you a good hint who is very experienced with the codebase and its structure.
Two metrics I find useful to know where to refactor: Files with the most commits and with the most authors.
- paulddraper 8y agoCommits per hour is interesting to understand CI/CD requirements.
- sftwds 8y agoThe 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-quick-stats#L195 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 8y agoNot 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.
- jlg23 8y agoYou are right, IMHO, but you are also wrong: "commits by hour" and "top committers" are the same metric simply applied to time frames.
- rgrau 8y agoIn a new job/project, knowing the span of dates per author gives me an idea of the churn of the company, and how long are people staying there. I had a script to do it and when I discovered this project I contributed this feature