Unable to connect GitLab with Visual Studio Code

Question

I'm using a self-hosted GitLab instance deployed for the company, along with Visual Studio Code.

I downloaded the extension "GitLab Workflow" in Visual Studio Code, so I can see my GitLab projects hosted in the company instance.

During setup, I entered:

The company GitLab instance URL "https://XXXXXXXXXXXXXXXXXXXXXXXXXX"
The PAT (personal access token) related to my personal space that contains all my projects.

I also entered the below URL in the configuration file of Visual Studio Code: Settings → Extensions → Gitlab Workflow → Instance URL as described in this article, section: Setup / Step 2:

 {
     "window.zoomLevel": -1,
     "workbench.colorTheme": "Visual Studio Dark",
     "terminal.integrated.shell.windows": "C:\\windows\\System32\\WindowsPowerShell\\v1.0\\powershell.exe",
     "gitlab.instanceUrl": "https://XXXXXXXXXXXXXXXXXXXXXXXXXX"
 }

But when trying to see my GitLab projects from VS Code, I get this error message:

 Failed to parse GitLab API response
 Command failed with exit code 128: git ls-remote --get-url
 fatal: No remote configured to list refs from.
 Error: Command failed with exit code 128: git ls-remote --get-url
 fatal: No remote configured to list refs from.
  at makeError (c:\Users\XXXXXXX\.vscode\extensions\gitlab.gitlab-workflow-3.9.0\node_modules\execa\lib\error.js:59:11)
  at handlePromise (c:\Users\XXXXXXX\.vscode\extensions\gitlab.gitlab-workflow-3.9.0\node_modules\execa\index.js:114:26)
  at processTicksAndRejections (internal/process/task_queues.js:94:5)

score 2 · Answer 1 · edited Jul 31 '21 at 09:50

2

It sounds like the extension doesn't know what remote to fetch from GitLab (a configuration issue rather than connection). Try adding this to your settings.json file:

"gitlab.remoteName": "origin",

If you use a different remote name, then replace "origin" with your remote. You can see the details of your remote using Git:

git remote

edited Jul 31 '21 at 09:50

Peter Mortensen

30,738
21
105
131

answered Jan 15 '21 at 20:48

Adam Marshall

6,369
1
29
45

1

Oddly, gitlab.remoteName doesn't appear to have a default value of `origin`. This answer resolved that for me. Thank you! – Josiah Aug 31 '21 at 15:17
2

Looks like they changed it to gitlab.pipelineGitRemoteName – AndrewKS Nov 25 '21 at 18:55

score 2 · Accepted Answer · edited Jul 31 '21 at 09:51

2

Visual Studio Code includes native capability to connect with GitLab.

At "Start", click on "clone repository" and then paste the target URL at the navigation bar:

edited Jul 31 '21 at 09:51

Peter Mortensen

30,738
21
105
131

answered Jan 19 '21 at 10:59

CloudRock

159
2
5
14

score 0 · Answer 3 · answered Dec 06 '21 at 05:00

0

I found this answer on their docs, if you already using Windows you should turn off your http.systemCertificates in VSC setting.json

thanks to this answer here

answered Dec 06 '21 at 05:00

Hamed

317
1
8

Unable to connect GitLab with Visual Studio Code

3 Answers3