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 GitHub credentials every time you pull or push a repository.
Lorsque Git vous invite à entrer votre mot de passe, entrez votre personal access token. Vous pouvez également utiliser une assistance d’informations d’identification comme Git Credential Manager. L’authentification par mot de passe pour Git a été supprimée en faveur de méthodes d’authentification plus sécurisées. Pour plus d’informations, consultez « Gestion de vos jetons d'accès personnels ».
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.
If you are an Enterprise Managed User, and your enterprise owners do not have the SSO Redirect setting enabled for the enterprise, then credential caching may not work properly when using Git Credential Manager (GCM). You will need to disable GCM account filtering locally in this situation to prevent getting prompted for authentication each time you perform a Git operation. For more details, see Mise en cache de vos informations d’identification GitHub dans Git.