The key is that you use https, which does not use the ssh channel, so the key is useless. To save the password for https, please refer to http://git.oschina.net/oschina/git-osc/issues/2586, if you want ssh+ Key does not require a password to submit, and the remote branch needs to use the SSH protocolgit@github.com:xx/xx.git
It is normal to enter the password when pushing. You can take some measures to omit this step:
Use SSH instead of https link
Add your SSH public key in Github
About the issue of .gitignore:
If you want to ignore all files starting with Runtime under www/Application/ in the project and directory, just remove the / in front of www, / represents the root directory
Changed the protocol and used git+ssh to configure according to the article http://www.ctrlqun.com/linux_..., everything is OK, no need to re-enter the password
The key is that you use https, which does not use the ssh channel, so the key is useless. To save the password for https, please refer to http://git.oschina.net/oschina/git-osc/issues/2586, if you want ssh+ Key does not require a password to submit, and the remote branch needs to use the SSH protocol
git@github.com:xx/xx.git
It is normal to enter the password when pushing. You can take some measures to omit this step:
About the issue of .gitignore:
If you want to ignore all files starting with Runtime under www/Application/ in the project and directory, just remove the / in front of www, / represents the root directory
Connect using ssh
.gitignore’s path is relative to the repo itself.
Changed the protocol and used git+ssh to configure according to the article http://www.ctrlqun.com/linux_..., everything is OK, no need to re-enter the password