Replies: 1 comment 1 reply
-
What’s actually causing the problemGitLens only recognizes a remote as GitHub if the hostname literally looks like Option 1 (easiest): Rename your SSH hosts to include “ If your SSH alias still contains the string github.com, GitLens will pick it up. Example: Then set your remote like: [email protected]:ORG/repository.git This works because GitLens scans for “github.com” in the hostname. Option 2: Keep the normal GitHub URL and let SSH pick the key Use a normal remote like: [email protected]:ORG/repository.git Then use Match rules or env vars in your SSH config to choose the right key. Option 3: Tell VS Code to treat your alias as GitHub If you really want to keep github-personal and github-org, you can:
It’s easy, but sometimes a bit flaky. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Seeing the following error when attempting to create a pull request from within GitLens (VSCode).
I suspect its because our organization is in the process of migrating between github organizations. Because of this, I have two SSH keys with config setup like this:
and my remote is defined like this:
org-xxxxxxx@github-personal:ORG/repository.gitBeta Was this translation helpful? Give feedback.
All reactions