DocsSettings

Code Analysis

Turn analysis on or off for each repository, choose the branch it follows, and rebuild it. Analysis starts when you add a repository, runs in the background, and resumes where it stopped.

Open the settings

Press ⌘, or choose Whaatcher › Settings…, then click the Code Analysis tab. Every repository you've added gets a row, and a long list scrolls.

Each row has a switch, the repository's name with a status line under it, and a ⋯ button.

Turn analysis on or off

Analysis is on for every repository you add. Use the switch at the left of a row to turn it off or back on. Turning it off stops the work but keeps what's stored, so turning it on later continues where it stopped.

What turning it off changes

With analysis off:

  • Overview shows Analysis is off for this repository and a Turn On Analysis button instead of results.
  • The Code tab of Insight leaves the repository out and names it after Analysis is off:.
  • Once Whaatcher restarts, OUTLINE in Files and Functions in Impact say Analysis pending, and 30D and SIMILAR stay empty. COG still shows, because it's measured from the file you open.

Analyzed Branch

Analysis follows one branch per repository, the Analyzed Branch, whatever you have checked out. To change it, click ⋯ and pick a local branch under Analyzed Branch. Automatic lets Whaatcher pick develop, then main or master, then the main worktree's branch, and shows its pick in parentheses. See Repositories and worktrees.

Switching asks first: Change and Rebuild deletes the stored analysis and rebuilds it for the new branch, which takes a while in large repositories. Dashboard cards also measure worktrees against this branch.

The status line

Under each name, the line shows the analyzed branch, with (auto) when Whaatcher picked it, then how many functions are stored and the analysis's size on disk, then the status:

  • analyzing 120 / 800: commits done out of the total.
  • waiting: waiting for its turn.
  • updated and a time: up to date.
  • off: analysis is turned off.
  • failed: point at it to see why.

not analyzed yet in place of the function count means nothing is stored yet. ? means the stored analysis couldn't be read; point at it for the reason.

Rebuild the analysis

Rebuild Analysis… in the ⋯ menu deletes the repository's stored analysis and builds it again from the start once you click Rebuild. It's available only while analysis is on. Until the rebuild finishes, screens that use the analysis show Analysis pending.

You rarely need it, because Whaatcher starts over on its own when it has to, such as after a force-push rewrites the analyzed branch. Use it when a repository keeps showing failed or ?.

Where the analysis is kept

Whaatcher keeps each repository's analysis as one file in ~/Library/Application Support/Whaatcher/Analysis, never inside the repository. It holds names and measurements, not your source code. Removing a repository from Whaatcher deletes its file, while its on/off and branch choices are kept by folder and come back if you add it again. See Data and privacy.