docs(evaluation): add custom evaluator bug bash guide#46183
docs(evaluation): add custom evaluator bug bash guide#46183ahmad-nader wants to merge 1 commit intoAzure:mainfrom
Conversation
Add bug-bash instructions and an AGENTS guide for the custom evaluator evaluation samples. Authored-by: GitHub Copilot Coding Agent Model: GPT-5.4 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
|
Thank you for your contribution @ahmad-nader! We will review the pull request and get back to you soon. |
|
@ahmad-nader please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.
Contributor License AgreementContribution License AgreementThis Contribution License Agreement (“Agreement”) is agreed to by the party signing below (“You”),
|
2 similar comments
|
@ahmad-nader please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.
Contributor License AgreementContribution License AgreementThis Contribution License Agreement (“Agreement”) is agreed to by the party signing below (“You”),
|
|
@ahmad-nader please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.
Contributor License AgreementContribution License AgreementThis Contribution License Agreement (“Agreement”) is agreed to by the party signing below (“You”),
|
There was a problem hiding this comment.
Pull request overview
Adds bug-bash documentation intended to help participants validate custom/friendly evaluator upload and end-to-end evaluation result correctness, plus an AGENTS.md guide to drive an automation assistant through the bug bash flow.
Changes:
- Added a bug bash guide for custom evaluator upload and validation scenarios.
- Added an
AGENTS.mdpersona/instructions file for automating the bug bash walkthrough.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 7 comments.
| File | Description |
|---|---|
| sdk/evaluation/azure-ai-evaluation/samples/custom_evaluators/Bug-Bash.md | Adds bug bash instructions/scenarios for evaluator upload and result validation. |
| sdk/evaluation/azure-ai-evaluation/samples/custom_evaluators/AGENTS.md | Adds an agent guide to run the Bug Bash.md flow end-to-end. |
| @@ -0,0 +1,46 @@ | |||
| You are a bug bash automation assistant for the Azure AI Evaluation custom evaluators samples. | |||
|
|
|||
| Your job is to help the user run the bug bash in [Bug-Bash.md](c:/Users/ahmadnader/WSL/Ubuntu2404/azure-sdk-for-python/sdk/evaluation/azure-ai-evaluation/samples/custom_evaluators/Bug-Bash.md) end to end. | |||
There was a problem hiding this comment.
The link to Bug-Bash.md is an absolute local filesystem path (c:/Users/...). This will be broken for anyone else and on GitHub. Use a repo-relative link (e.g., ./Bug-Bash.md) instead.
| Your job is to help the user run the bug bash in [Bug-Bash.md](c:/Users/ahmadnader/WSL/Ubuntu2404/azure-sdk-for-python/sdk/evaluation/azure-ai-evaluation/samples/custom_evaluators/Bug-Bash.md) end to end. | |
| Your job is to help the user run the bug bash in [Bug-Bash.md](./Bug-Bash.md) end to end. |
| - when relevant, provide the shared project URL: `https://ai.azure.com/nextgen/r/e0PPodqSSMyGXVSZRms7XA,naposani,,np-int,default/home` | ||
| - when relevant, provide the shared project endpoint: `https://np-int.services.ai.azure.com/api/projects/default` | ||
| - instruct the user to fetch the API key from the project URL before running the samples |
There was a problem hiding this comment.
This file embeds a shared project URL/endpoint and instructs users to fetch an API key. In a public repo this can leak internal environment details and encourages handling secrets in docs. Replace with placeholders (or a note to obtain these values via internal channels) and avoid hardcoding internal hostnames/IDs.
| [sample_custom_eval_upload_simple.py](https://github.com/Azure/azure-sdk-for-python/blob/feature/azure-ai-projects/2.0.2/sdk/ai/azure-ai-projects/samples/evaluations/sample_custom_eval_upload_simple.py) | ||
| - Advanced custom evaluator upload sample: | ||
| [sample_custom_eval_upload_advanced.py](https://github.com/Azure/azure-sdk-for-python/blob/feature/azure-ai-projects/2.0.2/sdk/ai/azure-ai-projects/samples/evaluations/sample_custom_eval_upload_advanced.py) |
There was a problem hiding this comment.
The sample links are pinned to a feature branch (feature/azure-ai-projects/2.0.2). This is brittle and will break once the branch is deleted/renamed. Prefer relative links to files in this repo/branch, or pin to a tag/commit SHA that will remain valid.
| [sample_custom_eval_upload_simple.py](https://github.com/Azure/azure-sdk-for-python/blob/feature/azure-ai-projects/2.0.2/sdk/ai/azure-ai-projects/samples/evaluations/sample_custom_eval_upload_simple.py) | |
| - Advanced custom evaluator upload sample: | |
| [sample_custom_eval_upload_advanced.py](https://github.com/Azure/azure-sdk-for-python/blob/feature/azure-ai-projects/2.0.2/sdk/ai/azure-ai-projects/samples/evaluations/sample_custom_eval_upload_advanced.py) | |
| [sample_custom_eval_upload_simple.py](../../../../ai/azure-ai-projects/samples/evaluations/sample_custom_eval_upload_simple.py) | |
| - Advanced custom evaluator upload sample: | |
| [sample_custom_eval_upload_advanced.py](../../../../ai/azure-ai-projects/samples/evaluations/sample_custom_eval_upload_advanced.py) |
| git clone https://github.com/Azure/azure-sdk-for-python.git | ||
| cd azure-sdk-for-python | ||
| git checkout feature/azure-ai-projects/2.0.2 | ||
| cd sdk/ai/azure-ai-projects/samples/evaluations | ||
| ``` |
There was a problem hiding this comment.
These steps require checking out a specific feature branch and running sample_custom_eval_upload_simple.py / advanced.py, but those sample files are not present in the current repo tree under sdk/ai/azure-ai-projects/samples/evaluations. As written, the instructions will fail for readers on main; either add the referenced samples or update the doc to point at the sample entry points that actually exist in this repo.
| - `np-int` is in the `INT` environment hosted in `Central US EUAP` | ||
| - project URL: `https://ai.azure.com/nextgen/r/e0PPodqSSMyGXVSZRms7XA,naposani,,np-int,default/home` | ||
| - project endpoint: `https://np-int.services.ai.azure.com/api/projects/default` | ||
| - fetch the API key from the project URL before running the samples | ||
|
|
There was a problem hiding this comment.
This section hardcodes a shared internal project URL and internal service endpoint. If this repository is public, this should not be published and it will also become stale quickly. Use placeholders and direct participants to request access/values via internal channels; avoid guidance that implies retrieving or pasting API keys from URLs.
|
|
||
| If you are using the shared project, configure the samples against `np-int` after access has been granted, verify that you can open the project URL successfully, use `https://np-int.services.ai.azure.com/api/projects/default` as the endpoint, and explicitly fill in the model variables required by the sample you are running. | ||
|
|
||
| ### 5.2 Required Variables For The Provided Samples |
There was a problem hiding this comment.
Section numbering is inconsistent: heading 5.2 appears before 5.1 later in the document. Please reorder/renumber to keep the steps sequential.
| Install the SDK package: | ||
|
|
||
| ```bash | ||
| pip install azure-ai-projects | ||
| ``` |
There was a problem hiding this comment.
This doc lives under azure-ai-evaluation samples, but the install step is for azure-ai-projects. This mismatch will confuse readers about which package they should be using. Consider moving this doc under the azure-ai-projects samples tree, or updating the instructions to use azure-ai-evaluation and its sample entry points.
Add bug-bash instructions and an AGENTS guide for the custom evaluator evaluation samples.
Authored-by: GitHub Copilot Coding Agent
Model: GPT-5.4
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 API spec, a link to the pull request containing these API spec changes should be included above.
All SDK Contribution checklist:
General Guidelines and Best Practices
Testing Guidelines