Skip to content

Fix copilot-setup-steps: relocate cache/tmp dirs to RUNNER_WORKDIR, add HOME - #31

Closed
JoseSantosAMD with Copilot wants to merge 1 commit into
JoseSantosAMD/intellikitfrom
copilot/sub-pr-24-b0e4c6bb-399c-4f7b-8331-a206cbf886c9
Closed

Fix copilot-setup-steps: relocate cache/tmp dirs to RUNNER_WORKDIR, add HOME#31
JoseSantosAMD with Copilot wants to merge 1 commit into
JoseSantosAMD/intellikitfrom
copilot/sub-pr-24-b0e4c6bb-399c-4f7b-8331-a206cbf886c9

Conversation

Copilot AI commented Mar 4, 2026

Copy link
Copy Markdown

The copilot-setup-steps.yml workflow was using github.workspace for pip/uv cache and temp directories, which caused failures on runners where the workspace may be read-only or reset between steps. The HOME variable was also unset, breaking tools that rely on it.

Changes

  • Environment variables — moved PIP_CACHE_DIR, UV_CACHE_DIR, TMPDIR, XDG_CACHE_HOME, and HOME to point under RUNNER_WORKDIR (persistent, writable across steps); removed the step-level UV_CACHE_DIR override that was redundant
  • Directory pre-creation — added explicit mkdir -p for all cache/tmp dirs at the start of the venv step so they exist before any tool tries to write to them
  • pip --cache-dir flag — passed explicitly to all pip install calls to ensure the relocated cache is honoured regardless of env variable resolution order
  • Path quoting — consistently quoted all shell variable expansions ("$GITHUB_WORKSPACE", "$GITHUB_PATH", etc.) to guard against paths with spaces
  • --no-cache-dir → explicit cache dir — replaced the earlier --no-cache-dir workaround with a proper writable cache location

🔒 GitHub Advanced Security automatically protects Copilot coding agent pull requests. You can protect all pull requests by enabling Advanced Security for your repositories. Learn more about Advanced Security.

Copilot AI mentioned this pull request Mar 4, 2026
Copilot AI changed the title [WIP] Add IntelliKit feature implementation Fix copilot-setup-steps: relocate cache/tmp dirs to RUNNER_WORKDIR, add HOME Mar 4, 2026
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