Skip to content

fix(ci): add COPILOT_API_KEY to e2e-canary workflow env#1960

Merged
Stephen Belanger (Qard) merged 1 commit intomainfrom
fix/copilot-api-key-canary
May 7, 2026
Merged

fix(ci): add COPILOT_API_KEY to e2e-canary workflow env#1960
Stephen Belanger (Qard) merged 1 commit intomainfrom
fix/copilot-api-key-canary

Conversation

@Qard
Copy link
Copy Markdown
Contributor

Summary

  • COPILOT_API_KEY was set as a GHA secret but was not listed in the explicit env: block of the e2e-canary job's run step
  • The subprocess running the copilot scenario inherits only the explicitly-listed env vars, so process.env.COPILOT_API_KEY was always undefined in that job
  • The key is already correctly wired in integration-tests.yaml (lines 62, 116); this aligns the canary job

Test plan

  • Trigger a canary run and confirm the github-copilot-instrumentation tests no longer fail with "Either COPILOT_API_KEY or BRAINTRUST_E2E_MODEL_BASE_URL must be set"

🤖 Generated with Claude Code

The key was set as a GHA secret but not forwarded to the canary step,
causing the copilot scenario subprocess to fail the "COPILOT_API_KEY
or BRAINTRUST_E2E_MODEL_BASE_URL must be set" guard. Already present
in integration-tests.yaml; this aligns the canary job.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@Qard Stephen Belanger (Qard) added the bug Something isn't working label May 7, 2026
@Qard Stephen Belanger (Qard) merged commit d701d12 into main May 7, 2026
44 checks passed
@Qard Stephen Belanger (Qard) deleted the fix/copilot-api-key-canary branch May 7, 2026 00:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants