Fix integration test: user-agent option failing due to orchestration ID in user-agent string by Copilot · Pull Request #709

Fix integration test: user-agent option failing due to orchestration ID in user-agent string by Copilot · Pull Request #709 · actions/github-script

The getUserAgentWithOrchestrationId function inserts actions_orchestration_id/... between the user-provided agent string and the octokit suffix, but the integration test was never updated to accommodate this format change.

Actual user-agent in CI:

actions/github-script actions_orchestration_id/37404db4-... octokit-core.js/7.0.6 Node.js/24

Test expected it to start with:

actions/github-script octokit-core.js/

Changes

.github/workflows/integration.yml — Replace glob-style != "$expected"* checks with =~ bash regex matching to allow the optional actions_orchestration_id/... segment between the user-provided agent and octokit-core.js/:

if [[ ! "$actual" =~ ^actions/github-script([[:space:]]actions_orchestration_id/[^[:space:]]+)?[[:space:]]octokit-core\.js/ ]]; then

This matches both environments where ACTIONS_ORCHESTRATION_ID is set (CI) and where it is not (local).

Original prompt

Fix the failing GitHub Actions workflow Integration test: user-agent option
Analyze the workflow logs, identify the root cause of the failure, and implement a fix.
Job ID: 68254844909
Job URL: https://github.com/actions/github-script/actions/runs/23458456807/job/68254844909

💬 Send tasks to Copilot coding agent from Slack and Teams to turn conversations into code. Copilot posts an update in your thread when it's finished.