Edit changes and commit to the branch directly, or start a pull request.
Since there're some huge repos containing thousands of folders/files (imagine someone uploaded node_modules/
), it'll significantly increase the responding time if we fetch all the files from GitHub API. Thus GitHub VSC will only search current folder when you are typing in the Cmd + P
panel.
Say the repo has the structure of foo/a/file1
and foo/b/file2
:
- When you typed
foo/
it will show the result as the combination offoo/a
andfoo/b
. - When you typed
foo/a/
it will show a single resultfoo/a/file1
.
Quote from GitHub docs:
Due to the complexity of searching code, there are a few restrictions on how searches are performed:
- Only the default branch is considered. In most cases, this will be the
master
branch.- Only files smaller than 384 KB are searchable.
Also, the global text search result has NO pagination yet. (It always shows page 1)