Commits Count is the total number of commits a single team member pushed to tracked repositories during the selected period. It's a raw activity signal — useful for confirming consistency, but never a productivity ranking on its own.
What it measures
The count of commits where this member is the author and committed_at falls within the period.
How Leanmote calculates it
commits_count = count(commits where author = member and committed_at in period)
Counts commits across all tracked repositories the member has access to.
Squash-merge commits typically count as one regardless of how many were squashed; per-repo configuration can adjust this.
Revert commits are excluded. Bot commits are not: a bot that Leanmote recognises is flagged as such on its own row, but its commits are still counted and still roll into the team total. Keep bots out of the team mapping if you don't want them in the number.
How to interpret it
Consistency matters more than volume. Steady commits over weeks beat heroic spikes.
Very low Commits Count with high PRs Created can indicate large, infrequent commits — coach toward smaller increments.
High Commits Count with low Reviews Count and low merges may indicate work that isn't being shipped.
What to do about it
Don't optimize for higher Commits Count. Many small commits aren't inherently better than fewer larger ones.
Use as a sanity check against PR activity and merges to confirm work is flowing.
Related metrics
PRs Created (per member)
Reviews Count (per member)
Activity distribution