|
|
|
|
|
by joshka
1184 days ago
|
|
If it's the product I think it is (I don't recall the exact name), it's not putting the repo into GPT. It's calculating embeddings on the code in the repo, storing those in a vector db and providing context from the store when processing questions about the repo. Effectively when you ask "how does foo work" becomes 1. lookup code items related to foo getting 1-N copies of code. 2. ask GPT "here is code related to foo <result from 1>. Now answer the following question: how does foo work" |
|
https://github.com/mpoon/gpt-repository-loader