Reindex files

[Urkman]

Copilot keeps working with outdated (changed) files.

Describe the bug When there are changes to a file, Copilot keeps working with the old outdated files. Even when I start a new chat or tell him to reload the files

It would be nice to have a way to manually reindex the files

[Urkman]

There is also a problem with reindexing the files internally. When doing changes in multiple steps he overrides the changes from the previous step. And this could get back and force, see my screenshot.

[Urkman]

Here one more example, where Copilot loses the context of it's own last changes to a file.

[lijie-lee]

Hi @Urkman, thanks for reaching out.

1. As to the issue Copilot keeps working with outdated (changed) files, Could you share more context like:

   • The version of GitHub Copilot for Xcode
   • The sample of the folder structure of the workspace / project
   • The log located at ~/Library/Logs/GitHubCopilot, named by github-copilot-for-xcode.log.

2. As to the Copilot loses the context of it's own last changes to a file, it may related to the editing file tool. The tool got improved within the latest version 0.38.0

[Urkman]

1.) This is easy to reproduce:

• just ask Copilot to add a function to a class.
• make manual changes to that class.
• ask Copilot to add another function to the class. Now the manual changes are reverted.

2.) This is still not solved, see screenshot. It's still a back and forth between adding and removing code...

Infos:

• Copilot Version: 0.38.0
• This is a default Xcode project, nothing special.

[vlad-roid]

I can confirm this is still the case, and extremely annoying to the point of rendering Copilot often useless. Basically as soon as you make a small change to a file, Copilot won't know it was changed until I specifically explain it. So with Copilot I not only have to look at what it did, I have to also keep track of the parallel dimension it's working on. See screenshots below where Copilot itself is explaining this pitfall and that there's supposedly no way to avoid it without being explicit about rechecking files and particular lines of code.