Hi, I sometimes need to push alot of bulk updates, and its too hard. I have to do:
git add .
git commit -m "blablabla"
git push origin master
type username
type password
git push origin2 master
type username
type password
Way to long for each plane! Especially since my password is longer than 30 characters. I have to update sometimes 6 or 7 at once. Not all have an origin2, but most do. Can I get rid of the passwords, and have Git remember them like gitlab uses?
[SOLVED] Too hard to push to GIThub
[SOLVED] Too hard to push to GIThub
Last edited by Octal450 on Sat Jun 11, 2016 1:49 am, edited 1 time in total.
Re: To hard to push to GIThub
https://help.github.com/articles/genera ... ssh-agent/
Get a ssh key. Upload the pubkey to github
https://help.github.com/articles/adding ... b-account/
And clone using ssh, instead of https:
Then you don't need to type passwords to push
Get a ssh key. Upload the pubkey to github
https://help.github.com/articles/adding ... b-account/
And clone using ssh, instead of https:
Then you don't need to type passwords to push
https://raw.githubusercontent.com/IAHM-COL/gpg-pubkey/master/pubkey.asc
R.M.S.
If we gave everybody in the World free software today, but we failed to teach them about the four freedoms, five years from now, would they still have it?
R.M.S.
If we gave everybody in the World free software today, but we failed to teach them about the four freedoms, five years from now, would they still have it?
Re: To hard to push to GIThub
OK, and how do I clone with ssh?
Re: To hard to push to GIThub
Click on "USE SSH" for the proper url
then, example
1. you had not cloned yet
Code: Select all
git clone git@github.com:FGMEMBERS/GulfstreamG550.git
Notice above how git@ is used instead of http://
2. you already cloned
Code: Select all
git remote -v
Response will show you origin pointing to a http:// url
example
Code: Select all
git remote remove origin
git remote add orgin git@github.com:FGMEMBERS/GulfstreamG550.git
git remote -v
Response will show you your origin now points to a ssh git@ url
https://raw.githubusercontent.com/IAHM-COL/gpg-pubkey/master/pubkey.asc
R.M.S.
If we gave everybody in the World free software today, but we failed to teach them about the four freedoms, five years from now, would they still have it?
R.M.S.
If we gave everybody in the World free software today, but we failed to teach them about the four freedoms, five years from now, would they still have it?
Re: To hard to push to GIThub
Instead of SSH...
You can use
And you won't have to retype your password for an hour. This is what I use on linux.
Or you can use the netrc file. See this link. Would be different instructions if not on Windows.
You can use
Code: Select all
git config --global credential.helper "cache --timeout=3600"
And you won't have to retype your password for an hour. This is what I use on linux.
Or you can use the netrc file. See this link. Would be different instructions if not on Windows.
OPRF Fighter Jock and Dev
Re: To hard to push to GIThub
Thx, won't have to reclone that way, let me try. I used 36000, to make the time longer
Re: To hard to push to GIThub
git: 'credential-cache' is not a git command. See 'git --help'.
Not working
Not working
Re: To hard to push to GIThub
Try typing it again. That error tells me you entered the wrong command.
For other techniques, see: https://git-scm.com/docs/git-credential-store
For other techniques, see: https://git-scm.com/docs/git-credential-store
OPRF Fighter Jock and Dev
Re: [SOLVED] Too hard to push to GIThub
that never ended up working, Israel and I switched to SSH.
Who is online
Users browsing this forum: No registered users and 8 guests