@@ -174,9 +174,9 @@ keys or passwords. You've certainly taken steps to avoid checking these into
174
174
your source repo, but they are fair game for LLMs to use as context and
175
175
training.
176
176
177
- Open the ` conf.ini ` or ` app.json ` file from the demo repo in the VS Code editor
178
- and examine the contents. In the Continue chat input, type ` @Files ` and select
179
- the file to include it as context, and ask Continue to explain the file.
177
+ Open the ` conf.ini ` or ` eth/ app.json` file from the demo repo in the VS Code
178
+ editor and examine the contents. In the Continue chat input, type ` @Files ` and
179
+ select the file to include it as context, and ask Continue to explain the file.
180
180
181
181
For example, using ` conf.ini ` :
182
182
@@ -204,13 +204,13 @@ Learn more in [Secrets encryption](./features/secrets-encryption.md).
204
204
205
205
### Assess dependency risk
206
206
207
- Open the ` packages .py` file from the demo repo in the VS Code editor and examine
208
- the import statements at the top. As with the previous step, type ` @Files ` , this
209
- time selecting the ` packages .py` file to add it to your prompt. Then ask
210
- Continue to analyze the file.
207
+ Open the ` python/app .py` file from the demo repo in the VS Code editor and
208
+ examine the import statements at the top. As with the previous step, type
209
+ ` @Files ` , this time selecting the ` python/app .py` file to add it to your prompt.
210
+ Then ask Continue to analyze the file.
211
211
212
212
``` plain title="Continue chat"
213
- @packages .py Please analyze this file
213
+ @app .py Please analyze this file
214
214
```
215
215
216
216
Using its up-to-date knowledge from
0 commit comments