0

I can't figure out the workflow on this. I keep getting the following error when trying to push to my repository:

fatal: could not read Username for 'https://github.com': No such file or directory

I've set up the repository on Github, then I git cloned it.

Locally it's fine. I made some changes to the README.md file. Then, I git add -Ad it, so the changes are ready. I then git commit -m '...'d it, and the commit is ready.

I set up the remote using: 

git remote add Midlife https://github.com/cireficc/Midlife.git

So now I should be able to git push Midlife master because the commit is ready to go. But no, I run into the 'could not read Username' error.

I've set up the local commit info using 

git config --global user.name "<my name>"
git config --global user.email "<my email>"

so I really don't know what's wrong.

It doesn't ask me for credentials but just gives me the error message quoted above, so I'm kind of lost.

Edit: This question is also a duplicate of: [dup1] -- [dup2] -- [dup3]

Community
  • 1
  • 1
Chris Cirefice
  • 5,475
  • 7
  • 45
  • 75

1 Answers1

1

That is a bug in current Git for Windows (version 1.8.5.2 aka Git-1.8.5.2-preview20131230).

You can see this thread for the discussion and instructions to fix it.

If a newer Git for Windows has been released, try installing that and see if it fixes the issue. If it doesn't please report it to the developers, and use an older version, the fix suggested in that thread, or an SSH remote instead.

Edit: As more users are still running into this problem, I have created an unofficial fix release 1.8.5.4 (Git-1.8.5.4-nevik20140208) which includes the fix for this bug presented in the mailinglist thread linked above. As of now (2014-02-09), there's no new official Git for Windows reease yet, so this should serve until there is one.

Nevik Rehnel
  • 49,633
  • 6
  • 60
  • 50
  • That's what it seems to be. What a nightmare. I've been trying to fix this for 2 hours... – Chris Cirefice Feb 02 '14 at 17:45
  • I'm most surprised at the fact that a new release has not been made. This issue is quite common (dunno if it appears for everyone), and Git 1.8.5.3 has been out for a while now. – Nevik Rehnel Feb 02 '14 at 17:48
  • Yeah I noticed that their last actual release was over a month ago. With such a (what I imagine to be) large-scale-impact bug, a new release should have been made, even if only to fix that single problem. It's unfortunate that they advertise the latest release as 'stable', when this is the first time I've used this version and couldn't even push 1 file. I'm sure the devs will get around to a new release soon :P – Chris Cirefice Feb 02 '14 at 17:53
  • As a workaround, I suspect the SSH URL should work (but of course you’ll have to setup keys). – Andrew Marshall Feb 02 '14 at 18:59
  • @ChrisCirefice I've created an unofficial fix release, as more users are still having this problem. If you've already applied the fix yourself, this might be a bit late. But feel free to spread the word if you know anyone else who is having this problem. (Link is added to my answer) – Nevik Rehnel Feb 09 '14 at 18:44