如果您使用的是HTTPS，请检查以确保URL是正确的。例如:

$ git clone https://github.com/wellle/targets.git
Cloning into 'targets'...
Username for 'https://github.com': ^C

$ git clone https://github.com/wellle/targets.vim.git
Cloning into 'targets.vim'...
remote: Counting objects: 2182, done.
remote: Total 2182 (delta 0), reused 0 (delta 0), pack-reused 2182
Receiving objects: 100% (2182/2182), 595.77 KiB | 0 bytes/s, done.
Resolving deltas: 100% (1044/1044), done.

如果您使用的是HTTPS，请检查以确保URL是正确的。例如:

$ git clone https://github.com/wellle/targets.git
Cloning into 'targets'...
Username for 'https://github.com': ^C

$ git clone https://github.com/wellle/targets.vim.git
Cloning into 'targets.vim'...
remote: Counting objects: 2182, done.
remote: Total 2182 (delta 0), reused 0 (delta 0), pack-reused 2182
Receiving objects: 100% (2182/2182), 595.77 KiB | 0 bytes/s, done.
Resolving deltas: 100% (1044/1044), done.

因为你使用的是HTTPS方式。HTTPS要求您每次尝试推或拉时都输入您的帐户访问权限，但也有一种方法，称为SSH，它让您告诉git，我给了您这台pc的帐户权限，并且永远不会再问我任何用户访问权限。要使用它，您必须生成SSH密钥，并将其添加到您的Github帐户，只需一次。要做到这一点，您可以遵循以下步骤

如何为Github生成SSH密钥

我刚刚收到一封来自github.com管理员的电子邮件，内容如下:“我们通常建议人们使用HTTPS URL，除非他们有特定的理由使用SSH协议。HTTPS更安全，更容易设置，所以我们在创建新的存储库时默认使用HTTPS。”

密码提示确实接受正常的github.com登录详细信息。关于如何设置密码缓存的教程可以在这里找到。我遵循了教程中的步骤，它对我很有效。

附加说明:

如果你已经添加了一个远程($git remote add origin…)并且需要更改特定的远程，然后首先执行远程删除($ git remote rm origin)，然后重新添加新的和改进的回购URL(其中“origin”是远程回购的名称)。

我们用原来的例子:

$ git remote add origin https://github.com/WEMP/project-slideshow.git
$ git remote rm origin
$ git remote add origin https://github-username@github.com/WEMP/project-slideshow.git

以下是官方给出的答案:

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: 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. You can configure Git to store your password for you. If you'd like to set that up, read all about setting up password caching.