Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update demo file references #39

Merged
merged 2 commits into from
Jan 16, 2025
Merged

Update demo file references #39

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
9b26173
Update demo file references
danbarr Jan 15, 2025
e0fbcbb
Fix formatting
danbarr Jan 15, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 8 additions & 8 deletions docs/quickstart-continue.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -174,9 +174,9 @@ keys or passwords. You've certainly taken steps to avoid checking these into
your source repo, but they are fair game for LLMs to use as context and
training.

Open the `conf.ini` or `app.json` file from the demo repo in the VS Code editor
and examine the contents. In the Continue chat input, type `@Files` and select
the file to include it as context, and ask Continue to explain the file.
Open the `conf.ini` or `eth/app.json` file from the demo repo in the VS Code
editor and examine the contents. In the Continue chat input, type `@Files` and
select the file to include it as context, and ask Continue to explain the file.

For example, using `conf.ini`:

Expand Down Expand Up @@ -204,13 +204,13 @@ Learn more in [Secrets encryption](./features/secrets-encryption.md).

### Assess dependency risk

Open the `packages.py` file from the demo repo in the VS Code editor and examine
the import statements at the top. As with the previous step, type `@Files`, this
time selecting the `packages.py` file to add it to your prompt. Then ask
Continue to analyze the file.
Open the `python/app.py` file from the demo repo in the VS Code editor and
examine the import statements at the top. As with the previous step, type
`@Files`, this time selecting the `python/app.py` file to add it to your prompt.
Then ask Continue to analyze the file.

```plain title="Continue chat"
@packages.py Please analyze this file
@app.py Please analyze this file
```

Using its up-to-date knowledge from
Expand Down
8 changes: 4 additions & 4 deletions docs/quickstart-copilot.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -129,9 +129,9 @@ keys or passwords. You've certainly taken steps to avoid checking these into
your source repo, but they are fair game for Copilot to send to its language
models as context.

Open the `conf.ini` or `app.json` file from the demo repo in the VS Code editor.
In the Copilot chat panel, observe that Copilot has automatically loaded the
active file as context.
Open the `conf.ini` or `eth/app.json` file from the demo repo in the VS Code
editor. In the Copilot chat panel, observe that Copilot has automatically loaded
the active file as context.

<ThemedImage
alt='Copilot chat showing the current file selected'
Expand Down Expand Up @@ -172,7 +172,7 @@ Learn more in [Secrets encryption](./features/secrets-encryption.md).

### Assess dependency risk

Open the `packages.py` file from the demo repo in the VS Code editor. Confirm
Open the `python/app.py` file from the demo repo in the VS Code editor. Confirm
that it's now the active context file in Copilot.

<ThemedImage
Expand Down
Loading