c116efe725
* New Crowdin translations by Github Action * Revert broken translated files to English * Revert broken translations * Revert broken translations * Revert more broket translations * Revert broken translation * Increase Node memory limit for running Jest * Allow Node to use more memory for Jest * Increase Node memory limit for running Jest Co-authored-by: Crowdin Bot <support+bot@crowdin.com> Co-authored-by: Chiedo <chiedo@users.noreply.github.com> Co-authored-by: James M. Greene <JamesMGreene@github.com>
1.5 KiB
1.5 KiB
title, intro, redirect_from, versions
| title | intro | redirect_from | versions | |||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Why is Git always asking for my password? | If Git prompts you for a username and password every time you try to interact with GitHub, you're probably using the HTTPS clone URL for your repository. |
|
|
Using an HTTPS remote URL has some advantages compared with using SSH. It's easier to set up than SSH, and usually works through strict firewalls and proxies. However, it also prompts you to enter your {% data variables.product.product_name %} credentials every time you pull or push a repository.
{% data reusables.user_settings.password-authentication-deprecation %}
You can avoid being prompted for your password by configuring Git to cache your credentials for you. Once you've configured credential caching, Git automatically uses your cached personal access token when you pull or push a repository using HTTPS.