I don't think that is a useful way to measure developer productivity. GitLab offers contribution analytics to get a good overview https://gitlab.com/help/analyt

I don't think that is a useful way to measure developer productivity. GitLab offers contribution analytics to get a good overview https://gitlab.com/help/analytics/contribution_analytics.md https://gitlab.com/help/analytics/contribution_analytics.md We find it a useful tool to have a data driven conversation between a manager and a report. But it should not form the basis of the performance review. That is why everyone should report to exactly one manager who understands what they do. The Gitlab performance review process is described on https://about.gitlab.com/handbook/people-operations/performance-reviews/ https://about.gitlab.com/handbook/people-operations/performa... (it is over 100 lines so I won't paste it here).