What does a normal workflow look like? #62
Replies: 1 comment
-
Hi, to refreshing embeddings you can simply re-vectorise files. This will remove existing embeddings for the files and ingest new embeddings to the database. To do this automatically, you can follow these steps in the wiki: https://github.com/Davidyz/VectorCode/wiki/Tips-and-Tricks#git-hooks or simply use the Edit: I do plan to introduce the |
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.
-
I'm using the nvim integration with
CodeCompanion
and I'm just curious what the normal workflow should be for ensuring that the embedding space is kept up to date?For instance do I need to drop the collection and reindex when switching between commits to ensure its completely up to date?
Is there a clever way to do this automagically? Maybe something like using the git log to look at file changes between commits and push those into the vector store
Claude came up with something like this for a script to refresh the store with those semantics - note that it's keeping a "commit" store which isn't specific to a project and there's no good way to delete a file yet using the CLI so it avoided that situation (lazy llm!) maybe removing a file should be a supported cli function?
If this is a normal workflow though maybe something like it should be supported natively?
Beta Was this translation helpful? Give feedback.
All reactions