Skip to content

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.

@singankit singankit requested a review from a team as a code owner October 3, 2024 23:34
@github-actions github-actions bot added the Evaluation Issues related to the client library for Azure AI Evaluation label Oct 3, 2024
@azure-sdk
Copy link
Collaborator

API change check

API changes are not detected in this pull request.

@singankit singankit enabled auto-merge (squash) October 7, 2024 05:30
@singankit
Copy link
Contributor Author

/check-enforcer override

@singankit singankit merged commit 886139f into main Oct 7, 2024
28 of 32 checks passed
@singankit singankit deleted the users/singankit/eval_run_properties branch October 7, 2024 16:52
l0lawrence pushed a commit to l0lawrence/azure-sdk-for-python that referenced this pull request Feb 19, 2025
* Adding properties needed by UI

* Updating tests

* Fixing linting issues

* Fixing formatting issues
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.

5 participants