Add smoke-copilot-aoai-apikey workflow for Azure OpenAI BYOK#37174
Merged
Conversation
Co-authored-by: zarenner <13670625+zarenner@users.noreply.github.com>
Copilot created this pull request from a session on behalf of
zarenner
June 5, 2026 19:10
View session
Collaborator
|
@copilot change model to o4-mini-aw |
Co-authored-by: zarenner <13670625+zarenner@users.noreply.github.com>
Contributor
Author
Updated |
zarenner
reviewed
Jun 5, 2026
Co-authored-by: zarenner <13670625+zarenner@users.noreply.github.com>
zarenner
reviewed
Jun 5, 2026
Co-authored-by: zarenner <13670625+zarenner@users.noreply.github.com>
Co-authored-by: zarenner <13670625+zarenner@users.noreply.github.com>
Contributor
There was a problem hiding this comment.
Pull request overview
This PR adds a new Copilot smoke-test workflow variant that routes Copilot engine traffic to an OpenAI-compatible Azure endpoint via BYOK credentials (FOUNDRY_OPENAI_ENDPOINT / FOUNDRY_API_KEY), and wires it into the repo’s command/label routing.
Changes:
- Added
smoke-copilot-aoai-apikeyworkflow markdown variant with BYOK provider env wiring. - Added the compiled lock workflow for the new variant.
- Updated
agentic_commands.ymlrouting metadata to include the new slash command andsmokelabel routing.
Show a summary per file
| File | Description |
|---|---|
| .github/workflows/smoke-copilot-aoai-apikey.md | New Copilot smoke workflow variant configured to use BYOK against a Foundry/AOAI OpenAI-compatible endpoint. |
| .github/workflows/smoke-copilot-aoai-apikey.lock.yml | Generated compiled workflow for the new variant. |
| .github/workflows/agentic_commands.yml | Adds the new command/workflow to routing so /smoke-copilot-aoai-apikey and smoke label can trigger it. |
Copilot's findings
Tip
Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
- Files reviewed: 2/3 changed files
- Comments generated: 3
| 7. Discussion interaction: get latest discussion with `github-discussion-query` (`limit=1`, `jq=".[0]"`), extract number, then `add_comment` to that discussion. | ||
| 8. Build: run `GOCACHE=/tmp/gh-aw/agent/go-cache GOMODCACHE=/tmp/gh-aw/agent/go-mod make build`. | ||
| 9. Artifact upload (only if build passes): stage `./gh-aw` at `$RUNNER_TEMP/gh-aw/safeoutputs/upload-artifacts/gh-aw` and call `upload_artifact` with `path: "gh-aw"`. | ||
| 10. Discussion create: call `create_discussion` in `announcements` with label `ai-generated`, title `copilot was here`, temp ID `aw_smoke_discussion`. |
| - Timestamp | ||
| - Pull request author and assignees | ||
|
|
||
| 2. **Set Issue Type** (**required**): Use the `set_issue_type` safe-output tool with `issue_number: "aw_smoke1"` (the temporary ID from step 1) and `issue_type: "Bug"` to set the type of the just-created smoke test issue. |
| - Overall status: PASS or FAIL | ||
| - Mention the pull request author and any assignees | ||
|
|
||
| 4. **Only if this workflow was NOT triggered by a pull_request event**: Use the `add_comment` tool to add a **fun and creative comment** to the newly created discussion (use the temporary ID `aw_smoke_discussion` from step 11) - be playful and entertaining in your comment |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Duplicates
smoke-copilot.mdassmoke-copilot-aoai-apikey.md(Smoke Copilot - AOAI (apikey)) to exercise the Copilot engine against an OpenAI-compatible Azure endpoint via BYOK usingFOUNDRY_API_KEY/FOUNDRY_OPENAI_ENDPOINT.Changes
.github/workflows/smoke-copilot-aoai-apikey.md— copy ofsmoke-copilot.mdwith:engine.envwiring BYOK to the OpenAI-compatible endpoint:slash_command.name,add-labels.allowed, bothclose-older-keys,create-check-run.name, the issue title, and the check-run title..github/workflows/smoke-copilot-aoai-apikey.lock.ymlvia./gh-aw compile --validate.Notes for review
COPILOT_PROVIDER_TYPEis intentionally left unset so the workflow exercises the defaultopenaiprovider path against the Foundry endpoint; AOAI old-style URLs (azureprovider type) can be covered by a separate variant later.COPILOT_PROVIDER_*credential vars are allowlisted by the Copilot engine (ADR-29411), so the${{ secrets.* }}references inengine.envpass strict-mode validation; the body text avoids${{ secrets.* }}literals to stay within the markdown expression allowlist.label_command(smoke) andremove-labels(smoke) are intentionally kept identical to the original so the existingsmokePR label triggers both variants.