Skip to content

Share RUNNER_TEMP with agent step in compiled lock.yml#35880

Draft
Copilot wants to merge 1 commit into
mainfrom
copilot/share-runner-temp-env-var
Draft

Share RUNNER_TEMP with agent step in compiled lock.yml#35880
Copilot wants to merge 1 commit into
mainfrom
copilot/share-runner-temp-env-var

Conversation

Copy link
Copy Markdown
Contributor

Copilot AI commented May 30, 2026

RUNNER_TEMP is used extensively in agent step shell scripts (e.g. ${RUNNER_TEMP}/gh-aw/actions/...) but was never explicitly declared in the step's env: block, unlike GITHUB_WORKSPACE which is already explicitly forwarded.

Changes

  • All engine execution steps (copilot, claude, codex, gemini, antigravity, crush, opencode, pi): add RUNNER_TEMP: ${{ runner.temp }} to the agent step env: map alongside the existing GITHUB_WORKSPACE entry
  • Test: assert RUNNER_TEMP is present in copilot engine step content
  • Golden fixtures + lock.yml: regenerated (236 files)

Result in compiled lock.yml:

        env:
          GITHUB_WORKSPACE: ${{ github.workspace }}
          RUNNER_TEMP: ${{ runner.temp }}   # new

Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Copilot AI changed the title Add RUNNER_TEMP env var to agent execution steps Share RUNNER_TEMP with agent step in compiled lock.yml May 30, 2026
Copilot AI requested a review from pelikhan May 30, 2026 06:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants