![]() ![]() However, due to security reasons, it is advisable that you use SSH to interact with GitHub, especially if you work for a company or you’re using a computer that isn’t yours. Git config -global credential.helper 'cache -timeout=600'īingo, you just fixed it, Git will never ask for your credentials again. You can also set a timeout for the above setting.Git config -global credential.helper cache Save the username and password for a session (cache it). ![]() Git config -global credential.helper store Git remote set-url origin Make Git store the username and password and it will never ask for them. Update the URL of origin remote using SSH instead of HTTPS.You can fix this by configuring Git to store your password for you. However, it also prompts you to enter your GitHub user credentials every time you pull or push a repository :(. Well using an HTTPS remote URL has some advantages: it’s easier to set up than SSH :), and usually works through strict firewalls and proxies. When you interact with a remote repository using HTTPS URLs on the command line, you’ll be asked for your GitHub username and password, this sucks right? These URLs work everywhere, even if you are behind a firewall or proxy. The clone URLs are available on all public and private repositories. In this article, I’ll show you how to fix this. Have you ever encountered Git asking you for your username and password every time you try to interact with GitHub even after configuring it? Well, this is a very common problem among users who use the HTTPS clone URL for their repository. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |