-
-
Notifications
You must be signed in to change notification settings - Fork 128
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
Error initiating new repo - "fatal: could not read Password..." #95
Comments
So I did "git pull" from terminal and it asked for my password. Not sure why it isn't using my SSH key, but maybe we could modify the plugin to prompt for password? |
Hum we potentially could prompt for the password but we would need to ask it every time as I don't really want to store it. Or maybe we could configure git to remember the password https://help.github.com/articles/caching-your-github-password-in-git/ |
I would definitely recommend saving the password in the Keychain. Terminal and SourceTree both do this, so it is standard behavior. |
One way you could get around this is by generating the files for pretty-diffs (Plugins > Git > Advanced > Generate files for pretty diffs) and committing with source tree or your tool of choice. If you want to use the password from the keychain, checkout the solution in #132. |
I believe this is solved. If it is not, please re-open. |
I am setting up a new repository and I received an error when clicking PULL from the plugin menu:
"fatal: could not read Password for 'https://username@server.company.com': Device not configured"
I initiated the repo via Terminal and I was attempting to commit/push the first file from Sketch. There was an error (not sure what) so instead I chose "init repo" from the plugin menu. I pasted the URL:
https://username@server.company.com/folder/repo_name.git
I attempted to do a pull, received the error.
Most of my git work has been via Sourcetree or Terminal, so it's possible that I screwed the setup up or something.
The text was updated successfully, but these errors were encountered: