Since I have the new version it doesnt ask me anymore for the password I set in my ssh key file.
It asks now directly for a github username and password when I push every time.
Is this a new feature of git or changed it in the past or is there something which changed on github?
I tried to authenticate using ssh and the email and password from my ssh key file and it worked.
GitHub changed to smartftp and also changed the instructions for setting up repos
https://github.com/blog/1104-credential-caching-for-wrist-friendly-git-usage
https://help.github.com/articles/create-a-repo
Saw it later, they use now https instead of the git protocol by default
I ran into this the other day when cutting-and-pasting from the new repository instructions on GitHub. Someone should probably file a bug report, because it confuses almost everyone I know.
The issue is that the instructions tell you to create a remote that uses the https protocol, rather than the git protocol. I typically use:
to populate a new GitHub repository from a pre-existing local one.
With https addresses, you have another option (beside the password caching):
Using an
_netrc
file, which will contain your username and password, in yourHOME
(or a.netrc
for bash session).Note that HOME isn't defined by default for Windows.
See also "Git - How to use
.netrc
file on windows to save user and password".(Other options at "Syncing with github")
you only input your username and password when you push first;after 3600s or 1 hour ,you push without username and password .
timeout you could set your number.