Codebase indexing: mark some directories as EXCLUDED #3368
Replies: 2 comments
-
|
I would additionally love to have a Afiter the LLM has read an They are useful for the LLM to find at the initial prompting, but afterwards when the LLM is just trying to find the actual code, they become noise and after a few attempts the LLM will fall back to This is also a micro-request for us to think about adding re-ranking to CBI. |
Beta Was this translation helpful? Give feedback.
-
|
Just learned about |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
We are talking about https://kilocode.ai/docs/features/codebase-indexing
OK, files in .gitignore are not indexed, right?
But, there are files that must be in repository - AND i do not want to have them in Kilocode index.
Some data files used to evaluate something, some E2E test data files for example... I have many of them, all in Git.
IntelliJ supports this: Right-click on some directory, select "Mark Directory as" from the context menu-> Select "Excluded"
In an ideal world, directories that are excluded in IntelliJ should be excluded from indexing in Kilo.
Probably the same for VSCode.
Kilocode CLI can just import these settings.
I would say, having fancy GUI is not a requirement - I can edit some config file.
Beta Was this translation helpful? Give feedback.
All reactions