You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Bug]: doesn't detect git submodules in the editor #2822
I searched existing issues and did not find a duplicate.
I included enough detail to reproduce or investigate the problem.
Area
apps/web
Steps to reproduce
Create or open a Git repository that contains at least one Git submodule.
Commit and initialize the submodule as usual (e.g. git submodule add ..., git submodule update --init), so the submodule’s files exist on disk.
Open this repository in the editor.
Try to reference a file from the submodule using the @ search (file/tagging) UI.
Type the exact file name or a unique substring from a file that lives inside the submodule.
Expected behavior
Files that live inside initialized Git submodules of the current repository should be indexed and appear in the @ search results, so they can be tagged and referenced like any other file in the repo.
Actual behavior
Files inside Git submodules are not detected at all:
The submodule directory itself is ignored by the @ search.
None of the files within the submodule appear in search results, even though they are present on disk and tracked in Git.
As a result, it is not possible to tag or reference any file that lives inside a Git submodule, which makes working with repos that rely on submodules effectively not usable.
Activity
juliusmarminge commentedon Jun 9, 2026
Duplicate of #997
Same gap — files inside git submodules aren't indexed for @-mentions / file search. #997 is the canonical issue (PR #1000 linked).