Fix the entire repo awareness please

Cody
, ,
1
  1. It seems like Codyignore is ruining context awareness for projects when you have many files that should be ignored.

Here is an example. I have set it up to ignore everything except the Scripts folder inside the Assets folder in my Unity project. At first glance, everything seems to be working correctly - only the files inside the Scripts folder can be discussed in the chat, etc. But if I ask questions about the entire repository - what is this project about? - no files from the context are used. And in response, I get some hallucinations based on the project name.

Not sure exactly, but I suspect that the levels of nesting play some role. Cody can avoid ignoring the Scripts folder even if it is inside the Assets folder. However, when addressing the entire repository through @, it cannot find anything at all in this case.

# Ignore everything
*.*
!.cody

# Don't ignore .gitignore and .codyignore
!.gitignore
!.cody/ignore

# Don't ignore Assets/Scripts directory
!/Assets/
/Assets/*
!/Assets/Scripts/

# Don't ignore .cs files in Assets/Scripts and its subdirectories
!/Assets/Scripts/**/*.cs

# Ignore everything else in Assets/Scripts
/Assets/Scripts/**/*
!/Assets/Scripts/**/*.cs
!/Assets/Scripts/**/*/
  1. And maybe add the option to switch off the entire repo context by default in the chat. In some cases, for example in game engines, you need to consider only a few scripts and ignore almost everything else. It’s just not wise to spend tokens on these. In my case for now it seems like the “entire repo” is actually nothing for Cody though.
1 Like