Skip to content

Commit ab130e9

Browse files
CopilotDanWahlin
andauthored
revert: remove changes to 02-context-conversations/README.md
Agent-Logs-Url: https://github.com/github/copilot-cli-for-beginners/sessions/394ba39c-c596-4806-868b-c6fa4474ac78 Co-authored-by: DanWahlin <1767249+DanWahlin@users.noreply.github.com>
1 parent 2c16bcc commit ab130e9

1 file changed

Lines changed: 0 additions & 15 deletions

File tree

02-context-conversations/README.md

Lines changed: 0 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -687,21 +687,6 @@ copilot
687687
688688
> 📖 **Learn more**: See [Additional Context Features](../appendices/additional-context.md#working-with-images) for supported formats, practical use cases, and tips for combining images with code.
689689
690-
### Attaching Document Files
691-
692-
In addition to the `@` syntax and image paste, you can attach supported document files (such as PDFs, Word documents, and text files) directly to your prompts. This lets Copilot read and reason about external reference material — for example, a requirements spec, a design document, or a README from another project.
693-
694-
When you start a prompt, look for the attachment option in the CLI interface to attach a file from your filesystem. Copilot will read the document's content and incorporate it into its response.
695-
696-
```bash
697-
copilot
698-
699-
# After attaching a document file (e.g. requirements.pdf), ask:
700-
> Based on the requirements I attached, what changes need to be made to @samples/book-app-project/book_app.py?
701-
```
702-
703-
> 💡 **When is this useful?** Use document attachment when you have reference material that isn't already in your codebase — like a design spec, an API contract, or a brief from a stakeholder. It's faster than copy-pasting large documents into your prompt.
704-
705690
</details>
706691
707692
---

0 commit comments

Comments
 (0)