DocsConcepts

Impact

Impact shows what a change touched and how far, set against this repository's usual, and puts first only what differs from it.

Where you see it

In Graph, click a commit or the Working tree row. The panel that opens shows Impact first, and a switch in it turns to the Changed Files list. Graph covers the panel.

What it shows

The summary line gives the files, the lines added and removed, and where this size sits, such as "Top 8% of this repo's commits". A treemap shows where the change landed and how much, Areas ranks the folders it changed, and Topics lists names that recur across the changed files.

This repository's usual

The usual is how each value is distributed across this repository's recent commits, by default the latest 500 without merges or automation accounts. With fewer than 100 earlier commits, Impact says it can't compare instead of calling anything usual.

Needs attention and As Usual

Spread, long-untouched files and repetition go under Needs attention when their value is in the top 10% of the usual. Size is marked on the summary line instead. Click a row to see its evidence. Everything within the usual goes under As Usual, one line each that opens into a list.

Signals

  • Spread: the change touched several folders that usually change separately.
  • Long-untouched files: it modified files that hadn't changed in the previous 500 commits.
  • Repetition: it gave the same edit to several functions.
  • Co-changed files: pairs that changed together again, or for the first time, stay under As Usual. A usually co-changed file left out of the change is flagged only when the two change together at least 80% of the time and, in this repository, files left out that way have tended to change soon after.
  • Tests: code changed but no test files did. This is flagged only when at least 90% of this repository's code commits also change tests.
  • Weight: public functions whose signature changed, that stopped being public, or that were deleted. It's a fact, not compared with the usual.

The same co-change history also feeds Neighbors, Hidden Coupling and Linked, which appear in Files, not in Impact.

Functions

When code analysis has read the change, Functions lists the changed functions with their Cognitive complexity before → after. For commits on the analyzed branch, Similar Functions points out similar functions left unchanged. See Cognitive complexity and Similar functions.

Changing the thresholds

The 10%, 80% and 90% lines and the commit counts are settings. Change them for all repositories or for one in Settings › Impact, and they apply right away. Impact settings explains each.