Caveats
What it cannot see, and what a copy cannot carry.
| Limit | What it means |
|---|---|
| What doctor cannot see | Only git's own records and two file formats that write their own path. Anything else that points into a directory, including a line in a shell profile or a process whose working directory is inside it, is invisible to the report. |
| What a clone cannot carry | Absolute paths inside files that doctor does not know the format of. A compiled artifact with a build path baked into it, a database with a stored data directory, a lockfile that recorded where it ran. They are copied faithfully and they still name the original. |
| Which filesystems can share blocks | A filesystem missing from this table is measured like any other, so the answer comes from the probe. |
How is this different from a fresh git clone?
A clone from a remote downloads the history again and gives you a checkout with nothing built in it. This copies the local directory, including everything git does not track, and pays for neither the download nor the build.
What doctor cannot see
Only git's own records and two file formats that write their own path. Anything else that points into a directory, including a line in a shell profile or a process whose working directory is inside it, is invisible to the report.