Open thedch opened 1 year ago
@thedch Thanks for reporting this issue and you are correct the VS Code extension is using the git remote to try to determine which repository it should request additional context about from the Cody App. When the repository does not have a git remote or it is unable to match the remote to a repository added to the Cody App the repository will show as not indexed within VS Code.
You can override the automatic codebase detection by using the Cody: Codebase
setting in VS Code. You should place the repo name exactly as it appears in the Cody App repositories list into the setting. Example below:
And what should we do on Windows in the same situation? there is no Cody App there
I am trying to embed a local code repo and use Cody with it in VS Code on MacOS. Other repos seem to be working, see #33.
However, when trying a repo that I have developed locally but does not have a git remote, the Cody VS Code extension does not seem to recognize it.
(I am not positive that the lack of git remote is the actual issue, it's just one clear difference that I notice, but could be something else).