Problem at initialising a git repository using VS Code [closed]

Question

Closed. This question needs details or clarity. It is not currently accepting answers.

Want to improve this question? As written, this question is lacking some of the information it needs to be answered. If the author adds details in comments, consider editing them into the question. Once there's sufficient detail to answer, vote to reopen the question.

Closed 8 months ago.

Improve this question

I have created one new file in an otherwise empty directory using VS Code. I went to version control and chose initialising this directory as a git repository. Now, a blue strip is moving around and a blue clock sign appeared on the git icon.

What does it wait for? With command line, git init is a no-brainer and lasts for a fraction of a second.

Hi! Are you connecting over ssh? What's your OS? Could be a permissions issue. If you click on the 3 dots up top, you can toggle Show Git Output — 1nternetz
– 1nternetz, Commented Sep 23, 2020 at 16:45
Thanks, interestingly, it was not just git init VS Code tried but lots of other commands. And, it wanted a repository with a remote counterpart. When initing... — Gergely
– Gergely, Commented Sep 23, 2020 at 17:17
How would ssh latency be involved in a local operation like git init? — eftshift0
– eftshift0, Commented Sep 23, 2020 at 19:16
@eftshift0 None, I was trying to get info on the operations VS Code was trying to run in the background. When you connect over ssh in VS Code over to a Linux machine, VS Code sets up a server on the remote machine to run the plugins. — 1nternetz
– 1nternetz, Commented Sep 24, 2020 at 12:50

1nternetz · Accepted Answer · 2020-09-24 12:51:52Z

1

If you click on the 3 dots up top, you can toggle Show Git Output. It will give you information on what commands VS Code is running in the background.

answered Sep 24, 2020 at 12:51

1nternetz

6505 silver badges7 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

Juergen Schulze · Accepted Answer · 2022-06-15 10:00:09Z

I had the same issue. Pressing "Initialize Repository" and nothing happens.

I think it's a problem with read/write rights of the project folder.

I am using Windows, but maybe it's also the same with Linux.

When creating a Laravel project with composer the issue occurs: hidden .git folder is created but nothing else happens.

When creating the project folder manually with file explorer and afterwards building the project with composer the issue is solved.

So my guess would be that composer messes up with folder creating somehow.

George Oyosa · Accepted Answer · 2022-08-31 17:58:34Z

0

Had the same issue. Turned to be some Folder Permissions issues. Solved by changing the folder permissions to the currently logged in user (yourself) and restarting VS Code.

For a detailed explanation, I followed this guide: Initialize Repository Not Responding #148023

answered Aug 31, 2022 at 17:58

George Oyosa

415 bronze badges

Collectives™ on Stack Overflow

Problem at initialising a git repository using VS Code [closed]

3 Answers 3

Comments

Comments

Comments

Hot Network Questions

Collectives™ on Stack Overflow

3 Answers 3

Comments

Comments

Comments

Related