Edmundo Carmona Antoranz <eantoranz@xxxxxxxxx> writes: > Given that worktrees are tracked in their own special fashion separately, > it makes sense to _not_ report them as "untracked". My gut feeling is that a much better solution to the unstated problem you are solving is to make sure that "git worktree add" will complain and not allow adding a subdirectory of any existing working tree of a repository as a new worktree. What problem are you trying to solve? "git add foo" where "foo" is actually a different worktree of the repository would add it as a submodule that causes confusion? If that is the case, I think the right solution is not to get into such a state, i.e. not create a worktree of the repository inside a different worktree in the first place.
