How do I avoid the specification of the username and password at every git push

Question

I git push my work to a remote Git repository   Every push will prompt me to input username and password  I would like to avoid it for every push  but how to configure to avoid it

User · Answer

Running the below command solved the problem for me.

git config --global credential.helper wincred

Please refer the below github documentation:

https://help.github.com/articles/caching-your-github-password-in-git/

User · Answer

You have to setup a SSH private key  you can review this page  how to do the setup on Mac  if you are on linux the guide should be almost the same  on Windows you would need tool like MSYS

User · Answer

My Solution on Windows    Right click at directory to push and select  Git Bash Here   ssh-keygen -t rsa  Press enter for all values  Check terminal for  Your public key has been saved in  c Users  lt your user name here gt   ssh id rsa pub Copy public key from specified file  Go to your GitHub profile    Settings    SSH and GPG keys    New SSH key    Paste your SSH key there    Save

User · Answer

Just use --repo option for git push command  Like this     git push --repo https   name password bitbucket org name repo git

User · Answer

I used the answer that Pavel suggested and it worked for me  My difference was to do it while I was adding the remote like so  git remote add  alias  https    name password  github com  the remote address  git

User · Answer

As far as I know  there are simply two safe ways  ssh or passwd encrypted using a keystore    SSH   Log in your github  Visit  https   github com settings keys  New SSH key  cat    ssh id rsa pub  paste it there  name and save it  if you have no such file  generate one for yourself by ssh-keygen -t rsa - just Enter for all prompts   Go to your local repository and update your remote by git remote set-url origin git ssh   git github com username reponame git - you can check it first by git remote -v   Here you go  just touch t  git add t  git commit -m  test   git push and confirm yes to enjoy the password-free world    passwd ENCRYPTED using a keystore  If you just use git config --global credential helper store as others mentioned  your unencrypted passwords will be just stored in a plain text under    git-credentials which is not safe as it sounds    Try to encrypt it as  sudo apt-get install libgnome-keyring-dev sudo make --directory  usr share doc git contrib credential gnome-keyring git config --global credential helper  usr share doc git contrib credential gnome-keyring git-credential-gnome-keyring  git config --global credential helper store      In this case  you are using https   git github com username reponame git

User · Answer

Saving Indefinitely  You can use the git-credential-store via   git config credential helper store   which stores your password unencrypted in the file system      Using this helper will store your passwords unencrypted on disk  protected only by filesystem permissions  If this is not an acceptable security tradeoff  try git-credential-cache  or find a helper that integrates with secure storage provided by your operating system     With a Timeout  Use the git-credential-cache which by default stores the password for 15 minutes   git config credential helper cache   to set a different timeout  use --timeout  here 5 minutes   git config credential helper  cache --timeout 300    Secure Saving Indefinitely  OS X and Windows         If you   re using a Mac  Git comes with an    osxkeychain    mode  which caches credentials in the secure keychain that   s attached to your system account  This method stores the credentials on disk  and they never expire  but they   re encrypted with the same system that stores HTTPS certificates and Safari auto-fills  Running the following on the command line will enable this feature  git config --global credential helper osxkeychain  You ll need to store the credentials in the Keychain using the Keychain app as well    If you   re using Windows  you can install a helper called    Git Credential Manager for Windows     This is similar to the    osxkeychain    helper described above  but uses the Windows Credential Store to control sensitive information  It can be found at https   github com Microsoft Git-Credential-Manager-for-Windows   emphases mine

User · Answer

1  Generate an SSH key  Linux Mac  Open terminal to create ssh keys   cd                    Your home directory ssh-keygen -t rsa     Press enter for all values   For Windows   Only works if the commit program is capable of using certificates private  amp  public ssh keys    Use Putty Gen to generate a key Export the key as an open SSH key   Here is a walkthrough on putty gen for the above steps  2  Associate the SSH key with the remote repository  This step varies  depending on how your remote is set up    If it is a GitHub repository and you have administrative privileges  go to settings and click  add SSH key   Copy the contents of your    ssh id rsa pub into the field labeled  Key   If your repository is administered by somebody else  give the administrator your id rsa pub  If your remote repository is administered by your  you can use this command for example    scp    ssh id rsa pub YOUR USER YOUR IP    ssh authorized keys id rsa pub   3  Set your remote URL to a form that supports SSH 1  If you have done the steps above and are still getting the password prompt  make sure your repo URL is in the form  git ssh   git github com username reponame git   as opposed to  https   github com username reponame git   To see your repo URL  run   git remote show origin   You can change the URL with   git remote set-url origin git ssh   git github com username reponame git    1  This section incorporates the answer from Eric P

User · Answer

If your PC is secure or you don t care about password security  this can be achieved very simply   Assuming that the remote repository is on GitHub and origin is your local name for the remote repository  use this command  git remote set-url --push origin https    lt username gt   lt password gt  github com  lt repo gt    The --push flag ensures this changes the URL of the repository for the git push command only    The question asked in the original post is about git push command only   Requiring a username password only for push operations is the normal setup for public repositories on GitHub   Note that private repositories on GitHub would also require a username password for pull and fetch operations  so for a private repository you would not want to use the --push flag       WARNING  This is inherently unsecure because    your ISP  or anyone logging your network accesses  can easily see the password in plain text in the URL  anyone who gains access to your PC can view your password using git remote show origin    That s why using an SSH key is the accepted answer   Even an SSH key is not totally secure   Anyone who gains access to your PC can still  for example  make pushes which wreck your repository or - worse - push commits making subtle changes to your code   All pushed commits are obviously highly visible on GitHub  But if someone wanted to change your code surreptitiously  they could --amend a previous commit without changing the commit message  and then force push it  That would be stealthy and quite hard to notice in practice    But revealing your password is worse   If an attacker gains knowledge of your username password  they can do things like lock you out of your own account  delete your account  permanently delete the repository  etc     Alternatively - for simplicity and security - you can supply only your username in the URL  so that you will have to type your password every time you git push but you will not have to give your username each time    I quite like this approach  having to type the password gives me a pause to think each time I git push  so I cannot git push by accident    git remote set-url --push origin https    lt username gt  github com  lt repo gt

User · Answer

Step 1 -  Create SSH keys on your linux system using below command  ssh-keygen -t rsa -b 4096 -C  your email    It will ask for passphrase and file name  default will be    ssh id rsa     ssh id rsa pub   Step 2 -  Once files created add public key id rsa pub to github account ssh section   Step 3 -  On your machine add private key id rsa to ssh-agent using below command  ssh-add    ssh id rsa    Step 4 -  Now add remote url git github com user name repo name git to your local git repo using below command   git remote remove origin git remote add origin git github com user name repo name git   Thats it

User · Answer

Appears that  at least when using TortoiseGIT on Windows  it is possible to create the SSH keys and transfer these to the GIT server using simply    gt  ssh-keygen exe  gt  ssh-copy-id  username   GIT server

User · Answer

All this arises because git does not provide an option in clone pull push fetch commands to send the credentials through a pipe  Though it gives credential helper  it stores on the file system or creates a daemon etc  Often  the credentials of GIT are system level ones and onus to keep them safe is on the application invoking the git commands  Very unsafe indeed   Here is what I had to work around  1  Git version  git --version  should be greater than or equal to 1 8 3   GIT CLONE  For cloning  use  git clone URL  after changing the URL from the format  http    myuser   my repo ip address   myrepo name git  to http    myuser   mypwd   my repo ip address   myrepo name git   Then purge the repository of the password as in the next section   PURGING   Now  this would have gone and   written the password in git remote origin  Type  git remote -v  to see the damage  Correct this by setting the remote origin URL without password   git remote set url origin http    myuser   my repo ip address   myrepo name git     written the password in  git logs in the repository  Replace all instances of pwd using a unix command like find  git logs -exec sed -i  s  my url with pwd   g         Here   my url with pwd  is the URL with password  Since the URL has forward slashes  it needs to be escaped by two backward slashes  For ex  for the URL http   kris passs123 192 168 0 1 proj git -  http       kris passs123 192 168 0 1   proj git   If your application is using Java to issue these commands  use ProcessBuilder instead of Runtime  If you must use Runtime  use getRunTime   exec which takes String array as arguments with  bin bash and -c as arguments rather then the one which takes a single String as argument   GIT FETCH PULL PUSH   set password in the git remote url as     git remote set url origin http    myuser   mypwd   my repo ip address   myrepo name git    Issue the command git fetch push pull  You will not then be prompted for the password  Do the purging as in the previous section  Do not miss it

User · Answer

Wire your git client to your OS credential store  For example in Windows you bind the credential helper to wincred   git config --global credential helper wincred   Is there a way to skip password typing when using https    on GitHub

User · Answer

Just wanted to point out something about the solution said above several times   git config credential helper store   You can use any command that requires a password after this  You don t have to push   you can also pull for instance  After that  you won t need to type in your username   password again

User · Answer

If you already have your SSH keys set up and are still getting the password prompt  make sure your repo URL is in the form  git ssh   git github com username reponame git   as opposed to  https   github com username reponame git   To see your repo URL  run   git remote show origin   You can change the URL with git remote set-url like so   git remote set-url origin git ssh   git github com username reponame git

User · Answer

Permanently authenticating with Git repositories  Run the following command to enable credential caching    git config credential helper store   git push https   github com repo git  Username for  https   github com    lt USERNAME gt  Password for  https   USERNAME github com    lt PASSWORD gt    Use should also specify caching expire  git config --global credential helper  cache --timeout 7200   After enabling credential caching  it will be cached for 7200 seconds  2 hours   Note  Credential helper stores an unencrypted password on a local disk

User · Answer

I was using the https link  https   github com org repo git  instead of the ssh link   git github com org repo git     Switching solved the problem for me

User · Answer

On Windows operating system use this instead  this works for me   https    Username   Password  github com  Username   repo  git   e g   git clone https    Username   Password  github com  Username   repo  git  git pull https    Username   Password  github com  Username   repo  git  git remote add origin https    Username   Password  github com  Username   repo  git  git push origin master

[git] How do I avoid the specification of the username and password at every git push?

Examples related to git

Examples related to github

Examples related to git-push