What this error means

Error: HttpError: Resource not accessible by integration OR remote: Permission to user/repo.git denied to github-actions[bot] OR Error: EACCES: permission denied, open '/home/runner/.npm/_cacache/...' is a GitHub Actions failure pattern reported for developers trying to fix github actions workflow permission errors including github_token scope issues, fork pr restrictions, and runner filesystem ownership conflicts from root vs non-root step runs. Based on the imported evidence, treat this as a tool-specific troubleshooting page rather than a generic API error.

Why this happens

FixDevs comprehensive guide documents all classes of GitHub Actions permission errors. Root causes include read-only default token permissions (post-2023), fork pull_request events getting read-only tokens regardless of settings, and root-owned files blocking subsequent non-root steps. Multiple error patterns covered: 403, EACCES, and filesystem ownership. Category mapping: GitHub Actions → GitHub Actions.

Common causes

  • FixDevs comprehensive guide documents all classes of GitHub Actions permission errors. Root causes include read-only default token permissions (post-2023), fork pull_request events getting read-only tokens regardless of settings, and root-owned files blocking subsequent non-root steps. Multiple error patterns covered: 403, EACCES, and filesystem ownership. Category mapping: GitHub Actions → GitHub Actions.

Quick fixes

  1. Confirm the exact error signature matches Error: HttpError: Resource not accessible by integration OR remote: Permission to user/repo.git denied to github-actions[bot] OR Error: EACCES: permission denied, open '/home/runner/.npm/_cacache/...'.
  2. Check the GitHub Actions account, local tool state, and provider configuration involved in the failing workflow.
  3. Compare the failing environment with a known working setup, then change one configuration value at a time.

Platform/tool-specific checks

  • Verify the command, editor, extension, or API client that produced the error.
  • Compare local settings with CI, deployment, or editor-level settings when the error appears in only one environment.
  • Avoid deleting credentials, local model data, or project settings until the failing scope is clear.

Step-by-step troubleshooting

  1. Capture the exact error message and the command, editor action, or request that triggered it.
  2. Check whether the failure is account/auth, quota/rate, model/provider, local runtime, or deployment configuration.
  3. Review the source evidence below and compare it with your environment.
  4. Apply one change at a time and rerun the smallest failing action.
  5. Keep the working fix documented for the team or deployment environment.

How to prevent it

  • Keep provider/tool configuration documented.
  • Record non-secret diagnostics such as tool version, provider name, model name, and command path.
  • Add a lightweight check before CI or production workflows depend on the tool.