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.