Missing commits

Step 1

If you have missing commits, navigate to Missing data? under the Setup section.

Step 2

In Data check, input the commit SHA*.

*A commit SHA (often called commit hash or SHA-1) is the unique ID that Git gives to each commit.

Step 2.1

If the commit does not show up, check if the repository where the commit was pushed is selected for processing (Setup->Repositories).

Step 2.2

If the repository is not selected, please select it and wait until data appears for that repository. If the repository is selected, there might be multiple possibilities:

The commit was part of a squash, or the branch was deleted immediately after the PR was merged (we are unable to fetch these types of commits because they disappear from the .git history).
The commit is very new, and our processing has not yet been able to process it — please wait.
Something else — please contact us.

Step 3

If the commit shows up, the reason you're not seeing it might be the following:

The commit is hidden/ignored because of the outlier settings (merge commit, lines over the limit, has certain message, etc.); check Settings -> Outliers.

The commit is on a repository that is no longer included in reports or that repository is not included in your group.
The commit was made by a contributor who is either not merged, not included in metrics/team, or is merged incorrectly —> check this in team management.

Outliers

Ignore Extensions

Here you can choose to ignore certain file types from being included in the stats by mentioning their extensions.

Multiple values must be separated by comma (no spaces, or special characters).
For now we do not support multiple extensions (like .blade.php).
Changes will only affect the data processed from now on. Already processed data will not change.
The default ignored extensions will not be erased. You can only add new extensions to ignore.
By default, the following extensions are ignored: svg, gif, png, jpg, ttf, map, eot, woff, woff2, plist, 000, po, mo.

Ignore Paths

Here you can choose to ignore certain paths when calculating the stats.

Multiple values must be separated by comma.
Changes will only affect the data processed from now on. Already processed data will not change.
The default ignored paths will not be erased. You can only add new paths to ignore.
By default, the following paths are ignored: node_modules/, vendor/.
The format must contain ** in places where there can be anything matched in that place. A few examples: a) vendor/** will ignore all the files inside vendor/ b) /test/ will ignore anything that contains test in the path like firstPart/test/lastPart.html c) Paths might not start with /, for example /vendor/ will not find vendor/, but it will find something/vendor/something, you can use **vendor/ instead

Ignore Commits Message

Here you can choose to ignore certain commits based on their message.

The commits that have a message which will match the regex will be ignored.
You will be able to see the change immediately. There is no need for reprocessing.
If the regex is not valid, the setting will restore to default.
Example: if you set the setting to "/\bweb\b/i" then all the commits that have a message which contains the word "web" will be ignored.
By default, no specific message is ignored.

Commits LoC limit

Here you can choose to ignore certain commits based on their size.

You will be able to see the change immediately. There is no need for reprocessing.
By default, commits that have more than 8000 lines of code changed are ignored.