Fix `context is not defined` error in safeoutputs MCP backend by Copilot · Pull Request #18646 · github/gh-aw

Copilot · 2026-02-27T06:56:28Z

The create_pull_request (and close_pull_request) handlers in the safeoutputs MCP server fail at runtime because context — a global injected by actions/github-script — is undefined when the server runs as a standalone Node.js process.

Changes

actions/setup/js/shim.cjs: Added a global.context shim alongside the existing global.core shim. When global.context is not already set, it constructs a context object from standard GitHub Actions environment variables, mirroring @actions/github's Context class shape:
- repo → parsed from GITHUB_REPOSITORY
- runId / runNumber → from GITHUB_RUN_ID / GITHUB_RUN_NUMBER
- payload → JSON-parsed from GITHUB_EVENT_PATH (empty object if unavailable)
- All other standard fields (sha, ref, actor, eventName, etc.)

The shim is a no-op when already running inside github-script. It's loaded at both MCP server entry points (safe-outputs-mcp-server.cjs, safe_inputs_mcp_server_http.cjs), so no additional wiring is needed.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

https://api.github.com/repos/actions/checkout/git/ref/tags/v3
- Triggering command: /usr/bin/gh gh api /repos/actions/checkout/git/ref/tags/v3 --jq .object.sha 4579/001/stability-test.md GO111MODULE ortcfg.link GOINSECURE ddfb0c316500b533rev-parse GOMODCACHE 4Op_icumgo8EKdHzMg/WeGoJ5R4ikM6s7pdmN96/PotExI9S0aYgU9eINNKU (http block)
https://api.github.com/repos/actions/checkout/git/ref/tags/v4
- Triggering command: /usr/bin/gh gh api /repos/actions/checkout/git/ref/tags/v4 --jq .object.sha -json GO111MODULE /opt/hostedtoolcache/go/1.25.0/x-test.short=true GOINSECURE GOMOD GOMODCACHE /opt/hostedtoolcache/go/1.25.0/x64/pkg/tool/linux_amd64/vet -uns�� runs/20260227-070428-28724/test-1160343831/.github/workflows /tmp/go-build2549672936/b050/vet.cfg .cfg GOSUMDB GOWORK 64/bin/go /opt/hostedtoolcache/go/1.25.0/x64/pkg/tool/linux_amd64/vet (http block)
- Triggering command: /usr/bin/gh gh api /repos/actions/checkout/git/ref/tags/v4 --jq .object.sha vaScript1463887172/001/test-frontmatter-with-arrays.md GO111MODULE /opt/hostedtoolcache/go/1.25.0/x64/pkg/tool/linux_amd64/vet GOINSECURE GOMOD GOMODCACHE /opt/hostedtoolcache/go/1.25.0/x64/pkg/tool/linux_amd64/vet -uns�� runs/20260227-070428-28724/test-643314917/.github/workflows /tmp/go-build2549672936/b078/vet.cfg 9672936/b359/vet.cfg l GOWORK 64/bin/go /opt/hostedtoolcache/go/1.25.0/x64/pkg/tool/linux_amd64/vet (http block)
https://api.github.com/repos/actions/checkout/git/ref/tags/v5
- Triggering command: /usr/bin/gh gh api /repos/actions/checkout/git/ref/tags/v5 --jq .object.sha -json .cfg 64/pkg/tool/linux_amd64/vet GOINSECURE GOMOD GOMODCACHE 64/pkg/tool/linux_amd64/vet env -json .cfg 64/pkg/tool/linux_amd64/vet GOINSECURE GOMOD GOMODCACHE 64/pkg/tool/linux_amd64/vet (http block)
https://api.github.com/repos/actions/github-script/git/ref/tags/v8
- Triggering command: /usr/bin/gh gh api /repos/actions/github-script/git/ref/tags/v8 --jq .object.sha npx prettier --cGOSUMDB GOPROXY 64/bin/go GOSUMDB GOWORK 64/bin/go sh -c "prettier" --che-errorsas node 64/bin/go tierignore format:cjs 64/bin/go go (http block)
- Triggering command: /usr/bin/gh gh api /repos/actions/github-script/git/ref/tags/v8 --jq .object.sha --check **/*.cjs 64/bin/go **/*.json --ignore-path ../../../.pretti-unreachable=false go env -json GO111MODULE 64/bin/go GOINSECURE GOMOD GOMODCACHE go (http block)
- Triggering command: /usr/bin/gh gh api /repos/actions/github-script/git/ref/tags/v8 --jq .object.sha "prettier" --check 'scripts/**/*GOINSECURE node 64/bin/go --write ../../../pkg/wor-atomic 64/bin/go go env -json GO111MODULE 64/bin/go GOINSECURE GOMOD GOMODCACHE go (http block)
https://api.github.com/repos/actions/setup-go/git/ref/tags/v4
- Triggering command: /usr/bin/gh gh api /repos/actions/setup-go/git/ref/tags/v4 --jq .object.sha -json GO111MODULE 1/x64/bin/node GOINSECURE GOMOD GOMODCACHE /opt/hostedtoolcache/go/1.25.0/x64/pkg/tool/linuTest User t-ha�� orts3096638588/001/main.md /tmp/go-build2549672936/b056/vet.cfg 9672936/b308/vet.cfg GOSUMDB GOWORK 64/bin/go /opt/hostedtoolcache/go/1.25.0/x64/pkg/tool/linux_amd64/vet (http block)
https://api.github.com/repos/actions/setup-node/git/ref/tags/v4
- Triggering command: /usr/bin/gh gh api /repos/actions/setup-node/git/ref/tags/v4 --jq .object.sha vaScript1463887172/001/test-frontmatter-with-nested-objects.md GO111MODULE /opt/hostedtoolcache/go/1.25.0/x64/pkg/tool/linux_amd64/vet GOINSECURE GOMOD GOMODCACHE /opt/hostedtoolcache/go/1.25.0/x64/pkg/tool/linux_amd64/vet -uns�� -unreachable=false /tmp/go-build2549672936/b051/vet.cfg 9672936/b332/vet.cfg GOSUMDB GOWORK 64/bin/go /opt/hostedtoolcache/go/1.25.0/x64/pkg/tool/linux_amd64/vet (http block)
https://api.github.com/repos/github/gh-aw/actions/runs/1/artifacts
- Triggering command: /usr/bin/gh gh run download 1 --dir test-logs/run-1 GO111MODULE 64/pkg/tool/linux_amd64/vet GOINSECURE GOMOD GOMODCACHE 64/pkg/tool/linux_amd64/vet env -json .cfg 64/pkg/tool/linux_amd64/vet GOINSECURE GOMOD GOMODCACHE 64/pkg/tool/linuremote.origin.url (http block)
https://api.github.com/repos/github/gh-aw/actions/runs/12345/artifacts
- Triggering command: /usr/bin/gh gh run download 12345 --dir test-logs/run-12345 GO111MODULE 64/pkg/tool/linu-lang=go1.25 GOINSECURE GOMOD GOMODCACHE 64/pkg/tool/linu-dwarf=false estl�� -json .cfg 64/pkg/tool/linu-nolocalimports GOINSECURE GOMOD GOMODCACHE 64/pkg/tool/linuorigin (http block)
https://api.github.com/repos/github/gh-aw/actions/runs/12346/artifacts
- Triggering command: /usr/bin/gh gh run download 12346 --dir test-logs/run-12346 GO111MODULE 64/pkg/tool/linu-nilfunc GOINSECURE GOMOD GOMODCACHE 64/pkg/tool/linu-tests estl�� g_.a GO111MODULE 64/pkg/tool/linux_amd64/vet GOINSECURE GOMOD GOMODCACHE 64/pkg/tool/linuTest User (http block)
https://api.github.com/repos/github/gh-aw/actions/runs/2/artifacts
- Triggering command: /usr/bin/gh gh run download 2 --dir test-logs/run-2 GO111MODULE 64/pkg/tool/linux_amd64/vet GOINSECURE GOMOD GOMODCACHE 64/pkg/tool/linux_amd64/vet env -json .cfg 64/pkg/tool/linux_amd64/vet GOINSECURE GOMOD GOMODCACHE 64/pkg/tool/linux_amd64/vet (http block)
https://api.github.com/repos/github/gh-aw/actions/runs/3/artifacts
- Triggering command: /usr/bin/gh gh run download 3 --dir test-logs/run-3 GO111MODULE 64/pkg/tool/linux_amd64/vet GOINSECURE GOMOD GOMODCACHE 64/pkg/tool/linux_amd64/vet env -json .cfg 64/pkg/tool/linux_amd64/vet GOINSECURE GOMOD GOMODCACHE 64/pkg/tool/linux_amd64/vet (http block)
https://api.github.com/repos/github/gh-aw/actions/runs/4/artifacts
- Triggering command: /usr/bin/gh gh run download 4 --dir test-logs/run-4 GO111MODULE 64/pkg/tool/linux_amd64/vet GOINSECURE GOMOD GOMODCACHE 64/pkg/tool/linux_amd64/vet env -json .cfg 64/pkg/tool/linux_amd64/vet GOINSECURE GOMOD GOMODCACHE 64/pkg/tool/linuremote.origin.url (http block)
https://api.github.com/repos/github/gh-aw/actions/runs/5/artifacts
- Triggering command: /usr/bin/gh gh run download 5 --dir test-logs/run-5 GO111MODULE 64/pkg/tool/linux_amd64/vet GOINSECURE GOMOD GOMODCACHE 64/pkg/tool/linux_amd64/vet env -json .cfg 64/pkg/tool/linux_amd64/vet GOINSECURE GOMOD GOMODCACHE 64/pkg/tool/linux_amd64/vet (http block)
https://api.github.com/repos/github/gh-aw/actions/workflows
- Triggering command: /usr/bin/gh gh workflow list --json name,state,path data/action_pins.json..." --check 64/bin/go **/*.ts **/*.json --ignore-path go list�� -mod=readonly -f 64/bin/go -- unsafe 64/bin/go go (http block)
- Triggering command: /usr/bin/gh gh run list --json databaseId,number,url,status,conclusion,workflowName,createdAt,startedAt,updatedAt,event,headBranch,headSha,displayTitle --workflow nonexistent-workflow-12345 --limit 100 main -lang=go1.25 go env -json GO111MODULE 64/bin/go GOINSECURE GOMOD GOMODCACHE go (http block)
- Triggering command: /usr/bin/gh gh run list --json databaseId,number,url,status,conclusion,workflowName,createdAt,startedAt,updatedAt,event,headBranch,headSha,displayTitle --workflow nonexistent-workflow-12345 --limit 6 GOMOD GOMODCACHE x_amd64/vet env ty-test.md GO111MODULE 64/pkg/tool/linux_amd64/vet GOINSECURE GOMOD GOMODCACHE 64/pkg/tool/linux_amd64/vet (http block)
https://api.github.com/repos/github/gh-aw/git/ref/tags/v1.0.0
- Triggering command: /usr/bin/gh gh api /repos/github/gh-aw/git/ref/tags/v1.0.0 --jq .object.sha ty-test.md GO111MODULE 64/pkg/tool/linux_amd64/vet GOINSECURE GOMOD GOMODCACHE 64/pkg/tool/linux_amd64/vet env 887119783/.github/workflows .cfg 64/pkg/tool/linux_amd64/vet GOINSECURE GOMOD GOMODCACHE 64/pkg/tool/linux_amd64/vet (http block)
https://api.github.com/repos/nonexistent/action/git/ref/tags/v999.999.999
- Triggering command: /usr/bin/gh gh api /repos/nonexistent/action/git/ref/tags/v999.999.999 --jq .object.sha -json rty 64/pkg/tool/linux_amd64/vet GOINSECURE GOMOD GOMODCACHE 64/pkg/tool/linux_amd64/vet env -json .cfg 64/pkg/tool/linux_amd64/vet GOINSECURE GOMOD GOMODCACHE 64/pkg/tool/linux_amd64/vet (http block)
https://api.github.com/repos/nonexistent/repo/actions/runs/12345
- Triggering command: /usr/bin/gh gh run view 12345 --repo nonexistent/repo --json status,conclusion GOINSECURE GOMOD GOMODCACHE x_amd64/vet env -json .cfg 64/pkg/tool/linux_amd64/vet on; \ echo "��git GOMOD GOMODCACHE 64/pkg/tool/linux_amd64/vet (http block)
https://api.github.com/repos/owner/repo/actions/workflows
- Triggering command: /usr/bin/gh gh workflow list --json name,state,path --repo owner/repo 64/bin/go GOSUMDB GOWORK 64/bin/go git -c log.showsignatur-errorsas log 64/bin/go -n1 --format=format:-atomic 0926890009f6 go (http block)
- Triggering command: /usr/bin/gh gh workflow list --json name,state,path --repo owner/repo 64/bin/go GOSUMDB GOWORK 64/bin/go /opt/hostedtoolc-buildtags -V=f�� (http block)
https://api.github.com/repos/owner/repo/contents/file.md
- Triggering command: /tmp/go-build2549672936/b381/cli.test /tmp/go-build2549672936/b381/cli.test -test.testlogfile=/tmp/go-build2549672936/b381/testlog.txt -test.paniconexit0 -test.v=true -test.parallel=4 -test.timeout=10m0s -test.run=^Test -test.short=true GOSUMDB GOWORK 64/bin/go sh -c "prettier" --che-errorsas node 64/bin/go --write ../../../pkg/wor-atomic 64/bin/go go (http block)
https://api.github.com/repos/test-owner/test-repo/actions/secrets
- Triggering command: /usr/bin/gh gh api /repos/test-owner/test-repo/actions/secrets --jq .secrets[].name prettier --check 64/bin/go **/*.ts **/*.json --ignore-path /bin/sh -c GOPATH=$(go env -errorsas sh 64/bin/go tierignore (http block)

If you need me to access, download, or install something from one of these locations, you can either:

Configure Actions setup steps to set up my environment, which run before the firewall is enabled
Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

Original prompt

This section details on the original issue you should resolve

<issue_title>[plan] Fix create_pull_request "context is not defined" error in safeoutputs MCP backend</issue_title>
<issue_description>## Objective

Fix the create_pull_request tool in the safeoutputs MCP backend that fails with context is not defined error.

Context

From audit discussion #18635 (2026-02-26→2026-02-27):

The Daily Documentation Updater successfully committed changes to branch docs/update-android-arm64-stem-commands-2026-02-27 but could not open a PR because create_pull_request failed 3 times with:
context is not defined
This is a backend error in the safeoutputs MCP server's create_pull_request handler.

Investigation Steps

Open actions/setup/js/safe_outputs_handlers.cjs (or equivalent handler file)

Find the create_pull_request handler function

Identify where context is referenced without being defined/passed

Check if context should be derived from the request parameters, environment, or a module import

Files to Investigate

actions/setup/js/safe_outputs_handlers.cjs — handler implementation

pkg/workflow/js/safe_outputs_handlers.cjs — if it exists

Any file containing create_pull_request handler logic in actions/setup/js/

Approach

Locate the create_pull_request handler in the safeoutputs JS codebase

Identify the undefined context variable reference

Fix the reference (likely needs to be extracted from the handler's parameters or from a GitHub client initialization)

Run make fmt-cjs && make lint-cjs to validate

Run make agent-finish before committing

Acceptance Criteria

create_pull_request handler no longer throws context is not defined

The handler correctly creates a PR in the target repository

make lint-cjs passes with no errors

Existing safe-output tests still pass

Generated by Plan Command for issue #discussion #18635

expires on Mar 1, 2026, 6:38 AM UTC

Comments on the Issue (you are @copilot in this section)
@pelikhan @copilot context is a global object that only exists in actions/github-script.
Add to shim.cjs</comment_new>

Fixes [plan] Fix create_pull_request "context is not defined" error in safeoutputs MCP backend #18643

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>

github-actions · 2026-02-27T09:14:17Z

Thanks for the fix, @Copilot 👋 — patching the missing global.context shim in actions/setup/js/shim.cjs is the right approach and the implementation cleanly mirrors the @actions/github Context class shape. The description is clear and the change is nicely focused.

One thing that would help get this across the finish line:

Add tests for shim.cjs — there is currently no shim.test.cjs in actions/setup/js/, even though every neighbouring module has a Vitest test file. The new global.context block has a few distinct branches worth covering: the no-op path (when global.context is already set), the environment-variable happy path, and the GITHUB_EVENT_PATH fallback (both successfully parsed and ignored-on-error).

If you'd like a hand, you can assign this prompt to your coding agent:

Add a Vitest test file at actions/setup/js/shim.test.cjs for the global.context shim introduced in shim.cjs.

Use the same structure as the other test files in that directory (e.g. create_pull_request.test.cjs):
  import { describe, it, expect, beforeEach, vi } from "vitest";

Cover the following scenarios:

1. No-op when global.context is already set
   - Set global.context to a sentinel object before requiring the shim
   - Assert that global.context is still the original sentinel after the require
   - Reset global.context to undefined in afterEach

2. Builds context from environment variables
   - Set process.env.GITHUB_REPOSITORY = "myorg/myrepo", GITHUB_SHA = "abc123", GITHUB_ACTOR = "alice", etc.
   - Clear global.context, then require shim.cjs
   - Assert global.context.repo equals { owner: "myorg", repo: "myrepo" }
   - Assert global.context.sha equals "abc123"
   - Assert global.context.actor equals "alice"

3. Handles missing GITHUB_REPOSITORY gracefully
   - Delete process.env.GITHUB_REPOSITORY
   - Assert global.context.repo equals { owner: "", repo: "" }

4. Reads payload from GITHUB_EVENT_PATH when the file exists
   - Write a temporary JSON file containing { "action": "opened" }
   - Set process.env.GITHUB_EVENT_PATH to its path
   - Assert global.context.payload equals { action: "opened" }

5. Silently ignores an unreadable GITHUB_EVENT_PATH
   - Set process.env.GITHUB_EVENT_PATH to a non-existent path
   - Assert that requiring the shim does not throw and global.context.payload equals {}

After writing the tests, run: make lint-cjs && make test-cjs (or the equivalent npm test command in actions/setup/js/) to confirm they pass.

Generated by Contribution Check

pelikhan · 2026-02-27T12:36:40Z

@copilot apply comment

Copilot · 2026-02-27T12:40:12Z

@copilot apply comment

The fix was already applied in commit 3b515a9 — global.context shim added to shim.cjs alongside the existing global.core shim. It builds the context object from GitHub Actions environment variables (GITHUB_REPOSITORY, GITHUB_RUN_ID, GITHUB_EVENT_PATH, etc.) so handlers like create_pull_request no longer throw context is not defined when running inside the MCP server.

Copilot

Pull request overview

Fixes runtime failures in the safe-outputs MCP backend when running outside actions/github-script by adding a standalone context global shim.

Changes:

Extend actions/setup/js/shim.cjs to also provide global.context (in addition to the existing global.core) when not running under github-script.
Build the shimmed context from standard GitHub Actions environment variables and (optionally) the JSON event payload file.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Copilot · 2026-02-27T13:05:17Z

actions/setup/js/shim.cjs

+  global.context = {
+    eventName: process.env.GITHUB_EVENT_NAME || "",
+    sha: process.env.GITHUB_SHA || "",
+    ref: process.env.GITHUB_REF || "",
+    workflow: process.env.GITHUB_WORKFLOW || "",


The shim claims to mirror @actions/github's Context shape, but the constructed object omits context.issue (a standard field/getter on Context). There are scripts in this repo that access context.issue.number (e.g. actions/setup/js/lock-issue.cjs and unlock-issue.cjs), which would still fail when run under this standalone shim. Consider populating an issue object (at least {owner, repo, number}) derived from payload.issue.number / payload.pull_request.number (and falling back to 0/undefined) to better match the real Actions context.

Initial plan

0926890

Copilot AI assigned Copilot and pelikhan Feb 27, 2026

Copilot started work on behalf of pelikhan February 27, 2026 06:56 View session

fix: add global.context shim to shim.cjs for MCP backend

3b515a9

Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>

Copilot AI changed the title ~~[WIP] Fix create_pull_request context is not defined error~~ Fix context is not defined error in safeoutputs MCP backend Feb 27, 2026

Copilot finished work on behalf of pelikhan February 27, 2026 07:07

github-actions bot added the needs-work label Feb 27, 2026

This was referenced Feb 27, 2026

[Contribution Check Report] Contribution Check — 2026-02-27 #18655

Closed

[Daily Report] Daily Status Report — 2026-02-27 #18656

Open

pelikhan approved these changes Feb 27, 2026

View reviewed changes

Copilot started work on behalf of pelikhan February 27, 2026 12:36 View session

github-actions bot mentioned this pull request Feb 27, 2026

[aw] No-Op Runs #18652

Open

Copilot finished work on behalf of pelikhan February 27, 2026 12:40

pelikhan marked this pull request as ready for review February 27, 2026 13:01

Copilot AI review requested due to automatic review settings February 27, 2026 13:01

pelikhan merged commit 971670d into main Feb 27, 2026
101 checks passed

pelikhan deleted the copilot/fix-create-pull-request-error-again branch February 27, 2026 13:01

Copilot started reviewing on behalf of pelikhan February 27, 2026 13:02 View session

Copilot AI reviewed Feb 27, 2026

View reviewed changes

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Fix `context is not defined` error in safeoutputs MCP backend#18646

Fix `context is not defined` error in safeoutputs MCP backend#18646
pelikhan merged 2 commits intomainfrom
copilot/fix-create-pull-request-error-again

Copilot AI commented Feb 27, 2026 •

edited

Loading

Uh oh!

github-actions bot commented Feb 27, 2026

Uh oh!

pelikhan commented Feb 27, 2026

Uh oh!

Copilot AI commented Feb 27, 2026

Uh oh!

Uh oh!

Copilot AI left a comment

Uh oh!

Copilot AI Feb 27, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Conversation

Copilot AI commented Feb 27, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Changes

I tried to connect to the following addresses, but was blocked by firewall rules:

Context

Investigation Steps

Files to Investigate

Approach

Acceptance Criteria

Comments on the Issue (you are @copilot in this section)

Uh oh!

github-actions bot commented Feb 27, 2026

Uh oh!

pelikhan commented Feb 27, 2026

Uh oh!

Copilot AI commented Feb 27, 2026

Uh oh!

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

Copilot AI Feb 27, 2026

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Copilot AI commented Feb 27, 2026 •

edited

Loading