Skip to main content

Increment visibility

Increment visibility section with a toggle and threshold

The "Hide increments above" toggle has a numeric threshold expressed in Calories. Once enabled, a single increment exceeding the threshold is excluded from the calculations, for example to filter out bulk, automatic commits (generated code, large merges) that distort the picture of everyday work.

The threshold field appears only after the toggle is enabled and accepts digits only, without separators or units.

A new organization starts with the toggle on and a threshold of 1000 Calories, set when the account is created. Until somebody changes this setting, one thousand applies.

Increments with a value strictly higher than the threshold are hidden, so an increment equal to the threshold in Calories stays visible.

Related mechanisms are File Pattern Exclusions and Excluding cherry-pick, revert and rebase. A manual decision about a single commit takes precedence over the threshold, so a commit manually included in statistics stays in them regardless of its value.

Comparison by effective Calories​

The threshold compares effective Calories, meaning the value after File Pattern Exclusions are applied. This is the same number the user sees next to the increment in the interface.

This has a practical effect when the exclusion patterns change: changing the pattern list alone, with the threshold untouched, moves some increments across the visibility boundary, in either direction. An increment that loses most of its files to the exclusions can therefore return to the views, even though nobody touched the threshold.

Scope of hiding​

A hidden increment disappears from charts and statistics and stops counting toward Retention and AI Adoption.

The threshold, however, skips all four health metrics calculated from pull requests, because a pull request is a record of a change's lifecycle, not an increment. For the Oversize PRs metric this is additionally intentional, since it measures the size of the pull request itself.

Excluding an entire repository from health metrics uses a separate toggle on the Sources list. This threshold does not serve that purpose.

Effect on historical data​

The threshold also covers increments scanned earlier, without rescanning the repositories. Changing the threshold value therefore recalculates visibility retroactively, across the entire available history.

Increments hidden or revealed manually are not touched by a threshold change. A human decision about a specific commit stays in force regardless of how the threshold is set afterward.

See also​