A 60-second guided demo

One changed file.
Where else should you look?

PatchRipple turns static import evidence into a small map of files that may deserve a closer look during review.

Synthetic exampleNo install to exploreOffline report
1changed pathsrc/core.ts
3static candidatesIncluding one related test
2 hopsto a possible dependentcore.ts ← api.ts ← ui.ts
Example pull request · example/projectSynthetic data
Static import relationships around the changed core module Arrows point from importers to the files they import. ui.ts imports api.ts, api.ts imports the changed core.ts, and core.test.ts imports core.ts. POTENTIAL DEPENDENTS CHANGED FILE src/ui.tsimports src/api.ts src/api.tsimports src/core.ts src/core.tschanged in this example src/core.test.tsimports src/core.ts Arrows point from an importer to its dependency.

The map is an aid for review. Open the report to select files and inspect base/head chains, owners, warnings, and source attribution.

Step 1 of 3

Start from src/core.ts

This example changes one path. The map shows static importers that may be worth checking in the pull request.

Changed: src/core.ts