From 9b26173b8fc0d61433043786fe2a7ccc801cd998 Mon Sep 17 00:00:00 2001 From: Dan Barr Date: Wed, 15 Jan 2025 14:22:54 -0500 Subject: [PATCH 1/2] Update demo file references --- docs/quickstart-continue.mdx | 8 ++++---- docs/quickstart-copilot.mdx | 4 ++-- 2 files changed, 6 insertions(+), 6 deletions(-) diff --git a/docs/quickstart-continue.mdx b/docs/quickstart-continue.mdx index edb4058..3a32519 100644 --- a/docs/quickstart-continue.mdx +++ b/docs/quickstart-continue.mdx @@ -174,7 +174,7 @@ 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 +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. @@ -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 +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 `packages.py` file to add it to your prompt. Then ask +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 diff --git a/docs/quickstart-copilot.mdx b/docs/quickstart-copilot.mdx index fdedba4..dac6bc2 100644 --- a/docs/quickstart-copilot.mdx +++ b/docs/quickstart-copilot.mdx @@ -129,7 +129,7 @@ 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. +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. @@ -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. Date: Wed, 15 Jan 2025 14:27:30 -0500 Subject: [PATCH 2/2] Fix formatting --- docs/quickstart-continue.mdx | 14 +++++++------- docs/quickstart-copilot.mdx | 6 +++--- 2 files changed, 10 insertions(+), 10 deletions(-) diff --git a/docs/quickstart-continue.mdx b/docs/quickstart-continue.mdx index 3a32519..9a065ea 100644 --- a/docs/quickstart-continue.mdx +++ b/docs/quickstart-continue.mdx @@ -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 `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. +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`: @@ -204,10 +204,10 @@ Learn more in [Secrets encryption](./features/secrets-encryption.md). ### Assess dependency risk -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. +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" @app.py Please analyze this file diff --git a/docs/quickstart-copilot.mdx b/docs/quickstart-copilot.mdx index dac6bc2..3e20fc9 100644 --- a/docs/quickstart-copilot.mdx +++ b/docs/quickstart-copilot.mdx @@ -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 `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. +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.