GitHub Actions extension fails with "Unable to connect to the GitHub API" in .code-workspace (works with Open Folder)
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- github-actions, typescript
- Domain
- devtools
Research direction
Reproduce the failure using the reported multi-root .code-workspace and compare it with opening the same repository through Open Folder. Trace the extension's workspace-mode repository resolution and activation path; done means GitHub Actions workflows and runs load in both modes without the API connection error.
Written by the indexing model from the issue text.
Description
Description
When I open the same repository via a multi-root .code-workspace, the GitHub Actions extension shows:
Unable to connect to the GitHub API, please check internet connection
If I open the repository directly with File → Open Folder, the extension works normally (workflows/runs load, authentication is fine).
This appears specific to workspace-mode repository resolution/activation, not network connectivity.
Steps to reproduce
- Create/open a multi-root workspace that includes this repo as a root:
c:\Users\<user>\Source\loom-workbench(plus other roots in workspace)
- Open VS Code using the
.code-workspacefile. - Open the GitHub Actions view.
- Observe error: "Unable to connect to the GitHub API, please check internet connection".
- Close VS Code.
- Reopen only
c:\Users\<user>\Source\loom-workbenchvia Open Folder. - GitHub Actions extension works correctly.
Expected behavior
The extension should authenticate and connect to GitHub API the same way in both:
- Open Folder mode
- .code-workspace (multi-root) mode
Actual behavior
- Open Folder: Works
- .code-workspace: Fails with API connection error
Environment
- Version: 1.125.1 (user setup)
- Commit: fcf604774b9f2674b473065736ee75077e256353
- Date: 2026-06-19T08:39:34Z
- Electron: 42.2.0
- ElectronBuildId: 14159160
- Chromium: 148.0.7778.97
- Node.js: 24.15.0
- V8: 14.8.178.14-electron.0
- OS: Windows_NT x64 10.0.26200
Additional context
- Internet connectivity is fine.
- Authentication/session is valid (confirmed by successful behavior in Open Folder mode).
- Reproducible consistently with the same repository and machine.
- Dominant language
- TypeScript
- Stars
- 661
- Forks
- 214
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from github/vscode-github-actions
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
github/vscode-github-actions#627 · 1 reaction ·
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
github/vscode-github-actions#630 · 1 reaction ·
-
long work Open
Difficulty 4/5 3-5 days Newbie friendliness 25/100
github/vscode-github-actions#628 ·
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 55/100
github/vscode-github-actions#625 ·
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 64/100
github/vscode-github-actions#621 · 3 comments ·
All issues in github/vscode-github-actions
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
security
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
IBM/node-sdk-core#373 ·
-
e2e-failure ready-to-code
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
chore
Difficulty 2/5 1-3 hours Newbie friendliness 88/100