This article covers common reasons for missing commits and duplicate commits.
Who can use this?
If you are unable to find a commit in one or all of your reports, check to see if any of the below reasons apply to your missing commit.
Are your repositories completely updated?
Sometimes your data might be in the process of updating. Your repos are updated approximately every 2-3 hours—so long as there is a connection to your repo. If your repositories are not successfully updating, learn more about blocked repositories for common causes and troubleshooting solutions.
Have you pushed your commit to the server?
Flow will not see your commit until it has been pushed to the server.
Is your commit hitting our outlier detection?
If you see a commit in the Work log but not in the Snapshot report you might be hitting our outlier detection. The Work log is a record of truth and will have all of your commits. If your commit is hitting outlier detection, it will not be included in calculations on any other report. We created outlier detection to remove commits from metrics that are likely not done by a real human in one day—things like minified js files, or importing a library.
Has your commit been squashed?
If your commit has been squashed, you will not see your original pre-squashed commit in Flow. Flow will display the revised commit post-squash since we look to Git for the record of truth for your commit data. If you would like more information on how we handle squashed commits, learn about squashing commits.
Has your commit been amended?
If your commit has been amended, just like squashing you will not see the original commit in your reports. Flow will display the revised commit post-amend since we look to Git for the record of truth.
Do you commonly Git push --force?
If you force push your local work to a remote server without pulling in new work that has recently been merged, you risk overwriting this work, thereby altering your Git history and deleting commits.
Still don't see the commit?
Email us at firstname.lastname@example.org and let us know.
If you're looking at the Work log or Check-in reports and notice two commits that look suspiciously similar, are they actually the same?
Flow filters by unique commit SHAs in all of the reports. So chances are, the duplicate commits you are seeing are actually unique.
To investigate duplicate commits:
- Navigate to the Check-in report.
- Click Show details under Commit complexity.
- View the commit details in the Commit complexity details.
Next, click on a link to the commit.
This takes you to your git host, where you can inspect the URL, and you should be able to see that the identifier at the end of the link (commit SHA) is unique.
Commits showing 0 lines of code
If your commit in one or all of your reports is returning with a message saying “0 lines of code affected,” this could be due to any of the following reasons:
The commit had no changes.
The commit had changes only in the files excluded from processing by the ignores file.
The commit is an outlier because it contains a greater number of lines of change than we allow in a single commit.
The commit is an outlier because it contains a greater number of files with changes than we allow in a single commit.
The change only consists of whitespace.
If you need help, please email email@example.com for 24/7 assistance.