In order words, it is not safe to assume that just because a file is within
the /project directory, that it belongs to repo A. As calling git is
expensive (~20-300ms depending on the machine, antivirus, etc.) we check for
.git folders manually, and only call git if one is found.
Symlinked files have the potential to further complicate this. If TypeScript's
preserveSymlinks option is on, then this may be passed the path to a symlinked
file. Unlike TypeScript, we will resolve the path, as the repo link should really
point to the actual file.
Responsible for keeping track of 0-N repositories which exist on a machine. This used to be inlined in SourcePlugin, moved out for easy unit testing.
Git repositories can be nested. Files should be resolved to a repo as shown below:
In order words, it is not safe to assume that just because a file is within the
/projectdirectory, that it belongs to repoA. As calling git is expensive (~20-300ms depending on the machine, antivirus, etc.) we check for.gitfolders manually, and only call git if one is found.Symlinked files have the potential to further complicate this. If TypeScript's
preserveSymlinksoption is on, then this may be passed the path to a symlinked file. Unlike TypeScript, we will resolve the path, as the repo link should really point to the actual file.