git ls-remote returns "fatal: No remote configured to list refs from."

Question

$ git ls-remote

results in

fatal: No remote configured to list refs from.

I have remotes defined

$ git remote

results in

personal_remote
upstream

score 5 · Answer 1 · edited Jul 19 '17 at 07:27

5

We can provide remote in the command:

git ls-remote personal_remote

Command worked for me on git version 1.9.1

edited Jul 19 '17 at 07:27

Pang

9,564
146
81
122

answered Apr 11 '17 at 06:12

user2992301

51
1
2

jthill · Accepted Answer · 2015-07-15T17:14:19.210

4

I can get this behavior in repos that have no origin remote. You can supply an alternate default remote name by setting remote.pushDefault.

edited Jul 15 '15 at 17:14

answered Jul 15 '15 at 17:03

jthill

55,082
5
77
137

1

@jthill correctly points out that `ls-remote` is expecting a remote with the name `origin`. The solution is to either rename one of the remotes to `origin` or use `remote.pushDefault` to tell `ls-remote` which to use. – eebbesen Feb 07 '17 at 15:01

score 1 · Answer 3 · answered Oct 16 '18 at 17:01

1

first git init it directory, then git clone the rep ../../something.git then go into that folder , then try git ls-remote. it should be good.

answered Oct 16 '18 at 17:01

senthil sivasamy

352
3
7

score 0 · Answer 4 · answered Oct 18 '17 at 09:29

If using git from VS Developer Command Prompt, it helps to change directory to the root of the git repository, i.e. the folder that contains the .git folder.

Running the git ls-remote command from there will pick up the remote repository from the directory.

git ls-remote returns "fatal: No remote configured to list refs from."

4 Answers4