[txutxu]

In my opinion, it's irrelevant, or it's not relevant without more information to extrapolate.

Scenario a)

A team is building trivial and already known features.

The real metric could be the number of features per developer, but still you could say "the more lines of code, did work faster than the less one"

Scenario b)

A developer is doing research all the day in a test environment, and just commit a single line of code to production git.

It increases the performance by x10.

Do you fire that person?

Source code commits are usefulness as a metric.

Features, tasks, number and impact of bugs, are better metrics, but for a developer team to work well, the main thing is good communication.