|
|
|
|
|
|
by sdesol
1576 days ago
|
|
|
> How about starting with mean time to merge a code change? I'm currently experimenting with using "Mode time" as I think it is less susceptible to data skew from outliers. See example below: https://oss.gitsense.com/insights/github?p=days-open&q=days-... For popular open-source projects that I used in the link above, the Mode time to merge is less than a day which is quite good in my opinion. And as you can expect, if you look at larger pull requests (>=10 file changes) the overall percentage drops by half as the link below shows: https://oss.gitsense.com/insights/github?p=days-open&q=pull-... I think what the link above shows is, you can't just willy-nilly use merge time to measure productivity, since there are a multiple variables at play. Full disclosure: The link that I referenced is my tool |
|
|