Git config -global -set credential.helper 'cache -timeout=3600'Ĭommand to step 3 (permanent storage): git config -global credential.helper store To control this time it is necessary to set the "timeout" parameter or change the strategy to permanently store the credentials by changing the "cache" to "store" like this:Ĭomplement command to step 3 (timeout in seconds): # timeout default is 900 seconds There is a concern with credential caching related to how long the token is stored.
To clear the token from the local computer: git config -global -unset credential.helper Run the command to retain the token in the credential.helper cache Ĭommand to step 3: git config -global credential.helper cache.
#Visual studio code github setup password
Enter the previously generated token as the password in the password field.If you have a lot of cloned repositories on your machine, I think the best way is to store the Github token in git credential.helper globally.Īssuming you have a token handy and are trying to run any git command that needs authentication, even within VSCode, the steps are: Solving those two issues allowed VSCode to start pushing with the proper credentials.Īre there too many cloned repositories? Storing the token globally will be easy to use. The remote URL registered in the local repository did include directly the token (instead of relying on the git credential manager).
#Visual studio code github setup windows
0 kommentar(er)
