Skip to content

Users/singankit/update evaluator prompts #40469

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

Draft
wants to merge 5 commits into
base: main
Choose a base branch
from

Conversation

singankit
Copy link
Contributor

Description

Please add an informative description that covers that changes made by the pull request and link all relevant issues.

If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.

All SDK Contribution checklist:

  • The pull request does not introduce [breaking changes]
  • CHANGELOG is updated for new features, bug fixes or other significant changes.
  • I have read the contribution guidelines.

General Guidelines and Best Practices

  • Title of the pull request is clear and informative.
  • There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

  • Pull request includes test coverage for the included changes.

@github-actions github-actions bot added the Evaluation Issues related to the client library for Azure AI Evaluation label Apr 10, 2025
@azure-sdk
Copy link
Collaborator

API change check

API changes are not detected in this pull request.

@@ -95,6 +95,8 @@ user:
**Query:** By what date must participants register to receive early bird pricing?
**Response:** Participants must register by May 31st to receive early bird pricing.

Note that the QUERY can either be a string with a user request or an entire conversation history including previous requests and responses from the assistant.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Note that the QUERY can either be a string with a user request or an entire conversation history including previous requests and responses from the assistant.
Note that the QUERY can either be a string with a user request or an entire conversation history including previous requests and responses from the assistant. And CONTEXT can either be a string with retrieved context or an entire conversation history including previous requests and responses from the assistant.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Evaluation Issues related to the client library for Azure AI Evaluation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants