Hi,
I’m working with repositories managed by the Google repo tool, which structures projects by placing the actual Git repositories under .repo/ and exposing working directories where .git is a symlink to the real repository.
Example:
.git -> ../../../../.repo/projects/.../project.git/
This is a valid Git setup and works correctly with:
- git CLI
- Git Extensions
- VS Code
However, Fork reports these directories as “not a repository”.
It seems Fork expects .git to be a real directory and does not resolve symlinks.
Request
Please add support for:
.git as a symbolic link to a directory
- (optionally)
.git as a gitdir: file (if not already fully supported)
Why this matters
- The
repo tool is widely used in large-scale projects (e.g. Android, embedded systems)
- Current behavior prevents using Fork in these environments
- Other Git clients work because they delegate repository resolution to Git itself
Thanks!
Hi,
I’m working with repositories managed by the Google
repotool, which structures projects by placing the actual Git repositories under.repo/and exposing working directories where.gitis a symlink to the real repository.Example:
.git -> ../../../../.repo/projects/.../project.git/
This is a valid Git setup and works correctly with:
However, Fork reports these directories as “not a repository”.
It seems Fork expects
.gitto be a real directory and does not resolve symlinks.Request
Please add support for:
.gitas a symbolic link to a directory.gitas agitdir:file (if not already fully supported)Why this matters
repotool is widely used in large-scale projects (e.g. Android, embedded systems)Thanks!