No GitHub repositories found when using SSH aliases
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 68/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- git, github-actions, typescript, vscode
- Domain
- developer-experience, tooling
Research direction
Start by tracing extension activation and the GitHub context lookup that fails with Invalid URL when the remote uses a non-github.com SSH alias. Reproduce with the SSH configuration and remote forms described in the issue, then verify that repository discovery works for both aliased and standard GitHub remotes.
Written by the indexing model from the issue text.
Description
Describe the bug
When using SSH config aliases (see the example below), the GitHub Actions extension returns the error message "No GitHub repositories found". SSH aliases are often used when a user has multiple GitHub accounts that have separate SSH keys.
This only occurs when using an alias that does not include github.com in the alias name. If I were to change the alias name to, for example, personal.github.com, as well as the remote, then the extension works without issue.
To Reproduce
Steps to reproduce the behavior:
- Create an alias in your SSH config file (e.g., ~/.ssh/config) with any name that does not include
github.com. - Switch your origin remote to use the alias (e.g., git@alias:username/repo.git)
- Reload VSCode
- Switch to the GitHub Actions extension and see "No GitHub repositories found"
- Switch your origin remote back to a standard "github.com" alias
- Reload VSCode
- Switch to the GitHub Actions extension and see standard functionality.
Expected behavior
GitHub Actions would work regardless of the SSH config alias.
Extension Version
v0.27.2
Additional context
Logs from the extension when using a non-github.com alias:
Activating GitHub Actions extension...
Error getting GitHub context
Invalid URL
TypeError: Invalid URL
at new URL (node:internal/url:818:25)
at /Users/josephgruber/.vscode/extensions/github.vscode-github-actions-0.27.2/dist/extension-node.js:1:1158030
at async Promise.all (index 0)
at async /Users/josephgruber/.vscode/extensions/github.vscode-github-actions-0.27.2/dist/extension-node.js:1:1157669
at async De (/Users/josephgruber/.vscode/extensions/github.vscode-github-actions-0.27.2/dist/extension-node.js:1:1157518)
at async os (/Users/josephgruber/.vscode/extensions/github.vscode-github-actions-0.27.2/dist/extension-node.js:1:1339675)
at async Lb.n (file:///Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:112:13382)
at async Lb.m (file:///Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:112:13345)
at async Lb.l (file:///Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:112:12801)
- 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 84/100
bcgov/bc-wallet-mobile#4761 · 1 comment ·
-
external-issue to-triage
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
area-deployment area-integrations triage:bot-seen
Difficulty 2/5 Half a day Newbie friendliness 86/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
refactor
Difficulty 2/5 1-3 hours Newbie friendliness 84/100