-
Notifications
You must be signed in to change notification settings - Fork 4.5k
DRAFT docs: ch 3 Sampling chapter #367
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.
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
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR adds a basic README file for the Sampling section in the Getting Started documentation. The change introduces a minimal documentation structure with just a title header.
Key Changes
- Creates a new README.md file with basic title for the Sampling section
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
| @@ -0,0 +1 @@ | |||
| # Sampling | |||
Copilot
AI
Aug 29, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The README file contains only a title header with no content. Since this is marked as a DRAFT, consider adding a brief description of what the Sampling section will cover, placeholder content sections, or a TODO list to guide future development.
|
yes it public |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
Copilot reviewed 1 out of 1 changed files in this pull request and generated no new comments.
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
Purpose
sampling is about delegation. The server tells the client I need help with this feature. The idea is that the server sends a sampling request to the client and the client uses its LLM to sample a response. This could be useful in many scenarios, everything from blog post abstract creation to creating a new product in a back office environment and more
Does this introduce a breaking change?
When developers merge from main and run the server, azd up, or azd deploy, will this produce an error?
If you're not sure, try it out on an old environment.
Does this require changes to learn.microsoft.com docs or modules?
which includes deployment, settings and usage instructions.
Type of change