[musingsole]

I submit pull requests based around a few hours throughout the day my team seems most likely to be between tasks (and so likely to check out a PR). Such as around 11 or 2 for pre/post lunch ramp down/up. Point being, the time my PRs are submitted has no bearing on when I did the work for that PR.

Using repo metadata to arrive at productivity metrics always strikes me as willfully bullheaded. If you timestamp my keystrokes, you can't know when I designed the algorithm I'm coding with those keystrokes. Spoiler alert: it was probably while I was falling asleep the night before.

[sdesol]

I wouldn't go as far as calling it "willfully bullheaded" as I do believe knowing when somebody creates a pull request can provide some data points worth mulling over. Having studied hundreds of popular open source projects, there does seem to be a pattern as to when people prefer to create a merge request, which is mid week.

I do agree that GitPrime, GitHub Insights and other similar solutions are pushing developer metrics in a dangerous direction, by latching onto low hanging fruit metrics. I written a bit about what I believe is a positive direction and this is focusing on impact, which I talk about at

https://news.ycombinator.com/reply?id=26457072&goto=threads%...