New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fatal: could not read Username for 'https://github.com': No error #230
Comments
Also running on Windows 10.
|
Try adding this into your git config
or via console
|
Came across this: https://github.com/Microsoft/Git-Credential-Manager-for-Windows
I was running git version 2.11. Updated to 2.16 and everything is working fine now. EDIT: clarify, I'm able to publish as before. |
This sure looks promising, @tadachi When I get back to my desktop I’ll gice this a shot. Good find! EDIT: again, good find! I was running |
Yep..., this works! Upgraded from 2.13 to 2.16... |
yes upgrade works for me too. thanks @cpilson |
I had the same issue, running |
Upgraded from 2.13.3 to 2.17.1 and the issue was resolved. |
My issue was not resolved by updating to v. 2.18. Need help |
@pun111 What do you see when you type |
Thanks a lot for replying. I see
I will happily provide more information as necessary, however I truly do not know what is important for you to best help me. I am running Windows 10, installed all pending updates today, uninstalled and reinstalled Git (with restarts), reinstalled VisualStudio. I have never had any problems with Git, the issue started a couple of days ago. No important update was installed AFAIK. In PowerShell I was getting Lastly, I tried This is still quite unfortunate, as there is obviously something wrong and moreover, I use VisualStudio Team Explorer which fails to work correctly when seeing any kind of fatal error. Any other solutions? Colleague suggested using TortoiseGit, but I honestly do not see how it could help. In my view I am running the correct versions and should be working fine as before |
@pun111 Try to delete (or rename) |
Oh yes, I forgot to mention, that was one of the first things I did. Thus the folder is not there anymore |
Okay it has to have something to do with the latest Visual Studio update. Just had the exact same thing happen to me on my Windows 7 laptop - after update, same problem. |
Had the same problem with a colleague laptop. What we did was delete the Git folder in Team Explorer, and then use Visual Studio installer to uninstall and reinstall its Git. The installer won't actually reinstall its Git (since the latest version already there - which we downloaded from git-scm.com) but it will do something... After it is done everything works.... cross your fingers... |
I thought I would update the thread for future users. Tthe issue was solved by updating the Credentials Manager. I think this version solved it https://github.com/Microsoft/Git-Credential-Manager-for-Windows/releases/tag/v1.17.0 but there have been new releases since |
I had this problem. Updating git from version |
Yep can confirm. updating git to latest version (2.19.1) solved the issue |
Upgrade to the latest version. problem will be solved. Worked for me!! |
hi. git config --global credential.helper wincred |
git update this worked for me |
uses git version 2.26.2.windows.1 but facing the same issue even after executing git config --global credential.helper wincred |
I also faced this problem |
Cloning into 'C:\Users\Shreedhar\twilio-video-react-hooks\node_modules.cache\gh-pages\git@github.com!akshaysk-ask!react-video-app.git'... Please make sure you have the correct access rights npm ERR! code ELIFECYCLE npm ERR! A complete log of this run can be found in: |
I am getting this error running the command on Ubuntu in a Github workflow. |
thanks man! |
Running under Windows 10.
"Nothing changed" in my local config. I was able to to a
git push
just prior to trying thisdeploy
, so I can communicate with the repo via CLI.I'd not pop up here, but I've been at this for a couple hours now and haven't made progress. Git CLI doesn't show a
Username
object, just auser
object.SET NODE_DEBUG=gh-pages&&yarn run deploy
The text was updated successfully, but these errors were encountered: