Why aren't my commits showing in Velocity?

This article covers the most common reasons commit activity may be missing and what steps you or your Velocity administrator can take to resolve it.

Merge commits may not include authored code changes and therefore might not appear in Velocity reports. Additionally, the merge strategy used—such as merge commits, squash, or rebase—can affect whether and how commit data is recorded.

How does squashing commits, rebasing, merging commits, and amending commits affect the different reports?

Velocity filters out some commits to ensure reports stay focused and meaningful. These include:

Trivial commits
Small changes—such as minor formatting or whitespace adjustments—are excluded from Velocity reports.

A commit is considered trivial when there are:

Duplicate commits
If the same commit appears on multiple branches (e.g., through rebasing or cherry-picking), Velocity will show it only once. Later appearances are filtered out as duplicates.

Velocity needs accurate contributor identities and repository connections to associate activity correctly.

Contributor identities
If the email address in your Git commit isn’t associated with a contributor profile in Velocity, the commit may be unmatched and won't appear in reports.

Repository connections
If you’re not seeing recent commits for a repository, there may be a connection issue between Velocity and your Git provider.

⚠️ Note: You won’t be able to view or resolve unmatched contributors or connection issues yourself. Please contact your Velocity admin to review these settings.

If your activity still seems to be missing, consider whether your commits were:

Your Velocity admin can also:

If you’ve reviewed all of the above and are still not seeing your work, contact Support for assistance.