blocks|key|4785412|text|我想你可能弄错了Git仓库的URL。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4785413|打开.git/config并找到远程“源”部分。确保您使用的是SSH：|offset|length|style|CODE|4785414|ssh://git@github.com/username/repo.git|code-block|syntax|javascript|4785415|如果单击Clone或download并选择ssh，则可以在存储库的主页中看到SSH+URL。|4785416|而不是https或git：|4785417|https://github.com/username/repo.git
git://github.com/username/repo.git|4785418|现在，您可以只使用SSH密钥而不是用户名和密码进行验证。|4785419|如果Git报告'origin'+has+already+been+added，请打开.config文件，并在[remote+origin]为url+=+ssh://github/username/repo.git后编辑url+=+"..."部件|4785420|4785421|其他服务也是如此。确保地址如下所示：protocol://something@url|4785422|例如，Azure+DevOps的.git/config：|BOLD|4785423|[remote+"origin"]
++++url+=+https://mystore@dev.azure.com/mystore/myproject/
++++fetch+=+%2Brefs/heads/*:refs/remotes/origin/*|4785424|entityMap^0|0|2|B|0|0|0|3|5|9|3|0|0|0|7|V|16|7|1I|F|1Y|10|31|B|0|0|I|O|0|3|P|G|B|0|0^^$0|@$1|2|3|4|5|6|7|16|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|17|8|@$D|18|E|19|F|G]]|9|@]|A|$]]|$1|H|3|I|5|J|7|1A|8|@]|9|@]|A|$K|L]]|$1|M|3|N|5|6|7|1B|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|1C|8|@$D|1D|E|1E|F|G]|$D|1F|E|1G|F|G]]|9|@]|A|$]]|$1|Q|3|R|5|J|7|1H|8|@]|9|@]|A|$K|L]]|$1|S|3|T|5|6|7|1I|8|@]|9|@]|A|$]]|$1|U|3|V|5|6|7|1J|8|@$D|1K|E|1L|F|G]|$D|1M|E|1N|F|G]|$D|1O|E|1P|F|G]|$D|1Q|E|1R|F|G]|$D|1S|E|1T|F|G]]|9|@]|A|$]]|$1|W|3|-4|5|6|7|1U|8|@]|9|@]|A|$]]|$1|X|3|Y|5|6|7|1V|8|@$D|1W|E|1X|F|G]]|9|@]|A|$]]|$1|Z|3|10|5|6|7|1Y|8|@$D|1Z|E|20|F|11]|$D|21|E|22|F|G]]|9|@]|A|$]]|$1|12|3|13|5|J|7|23|8|@]|9|@]|A|$K|L]]|$1|14|3|-4|5|6|7|24|8|@]|9|@]|A|$]]]|15|$]]

I think you may have the wrong Git repository URL. 

Open <code>.git/config</code> and find the [remote "origin"] section. Make sure you're using the SSH one:

<pre><code>ssh://git@github.com/username/repo.git
</code></pre>

You can see the SSH URL in the main page of your repository if you click Clone or download and choose ssh.

And NOT the <code>https</code> or <code>git</code> one:

<pre><code>https://github.com/username/repo.git
git://github.com/username/repo.git
</code></pre>

You can now validate with just the SSH key instead of the username and password. 

If Git complains that <code>'origin' has already been added</code>, open the <code>.config</code> file and edit the <code>url = "..."</code> part after <code>[remote origin]</code> as <code>url = ssh://github/username/repo.git</code>

<hr>

The same goes for other services. Make sure the address looks like: <code>protocol://something@url</code>

E.g. <code>.git/config</code> for Azure DevOps:

<pre><code>[remote "origin"]
 url = https://mystore@dev.azure.com/mystore/myproject/
 fetch = +refs/heads/*:refs/remotes/origin/*
</code></pre>

blocks|key|676183|text|配置credential.helper|type|unstyled|depth|inlineStyleRanges|entityRanges|data|676184|在OS+X(现在的macOS)上，在终端中运行此命令|676185|git+config+--global+credential.helper+osxkeychain|code-block|syntax|javascript|676186|它使Git能够使用文件Keychain.app来存储用户名和密码，并从密钥链中检索私有SSH密钥的密码短语。|676187|对于Windows使用：|676188|git+config+--global+credential.helper+wincred|676189|对于Linux使用：|676190|git+config+--global+credential.helper+cache+//+If+you+want+to+cache+the+credentials+for+some+time+(default+15+minutes)|676191|或|676192|git+config+--global+credential.helper+store+//+if+you+want+to+store+the+credentials+for+ever+(considered+unsafe)|676193|注意:第一个方法将在内存中缓存凭据，而第二个方法将以纯文本格式将它们存储在~/.git-credentials中。|offset|length|style|CODE|676194|有关Linux方法的更多信息，请查看here。|676195|有关这三个项目的更多信息，请查看here。|676196|故障排除|676197|如果正确配置了Git凭据助手，macOS会将密码短语保存在密钥链中。有时connection+between+SSH+and+the+passphrases+stored+in+the+keychain可能会崩溃。运行ssh-add+-K或ssh-add+~/.ssh/id_rsa将密钥再次添加到密钥链。|676198|macOS+v10.12+(+ssh+)对ssh的更改|676199|对于macOS+v10.12+(Sierra)，每次重新启动后都需要运行ssh-add+-K。要避免这种情况，请使用此内容创建~/.ssh/config。|676200|Host+*
++++AddKeysToAgent+yes
++++UseKeychain+yes
++++IdentityFile+~/.ssh/id_rsa|676201|在10.12.2上的ssh_config+man页面中：|676202|676203|+UseKeychain+On+macOS，指定在尝试使用特定密钥时，系统是否应在用户的密钥链中搜索密码短语。当用户提供密码短语时，此选项还指定密码短语在被验证为正确后是否应存储到密钥链中。参数必须为'yes‘或'no’。默认值为'no‘。|blockquote|BOLD|676204|676205|676206|苹果添加了Technote+2449，它可以解释发生了什么。|676207|676208|在macOS+Sierra之前，ssh会显示一个对话框，询问您的密码短语，并提供将其存储到密钥链中的选项。此UI在一段时间前已弃用，并已被删除。|676209|676210|entityMap|0|LINK|mutability|MUTABLE|url|https://www.tecmint.com/fix-git-user-credentials-for-https/|1|https://docs.github.com/en/free-pro-team@latest/github/using-git/caching-your-github-credentials-in-git|2|https://apple.stackexchange.com/questions/18458/password-dialog-appears-when-ssh-private-key-permissions-are-set-to-0600/139522#139522|3|https://developer.apple.com/library/content/technotes/tn2449/_index.html^0|0|0|0|0|0|0|0|0|0|0|11|I|0|I|4|0|0|G|4|1|0|0|31|A|3C|L|10|1T|2|0|0|10|A|1R|D|0|0|A|A|L|3|0|0|1|B|0|0|0|5|D|3|0|0|G|3|0|0^^$0|@$1|2|3|4|5|6|7|29|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|2A|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|2B|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|2C|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|2D|8|@]|9|@]|A|$]]|$1|M|3|N|5|F|7|2E|8|@]|9|@]|A|$G|H]]|$1|O|3|P|5|6|7|2F|8|@]|9|@]|A|$]]|$1|Q|3|R|5|F|7|2G|8|@]|9|@]|A|$G|H]]|$1|S|3|T|5|6|7|2H|8|@]|9|@]|A|$]]|$1|U|3|V|5|F|7|2I|8|@]|9|@]|A|$G|H]]|$1|W|3|X|5|6|7|2J|8|@$Y|2K|Z|2L|10|11]]|9|@]|A|$]]|$1|12|3|13|5|6|7|2M|8|@]|9|@$Y|2N|Z|2O|1|2P]]|A|$]]|$1|14|3|15|5|6|7|2Q|8|@]|9|@$Y|2R|Z|2S|1|2T]]|A|$]]|$1|16|3|17|5|6|7|2U|8|@]|9|@]|A|$]]|$1|18|3|19|5|6|7|2V|8|@$Y|2W|Z|2X|10|11]|$Y|2Y|Z|2Z|10|11]]|9|@$Y|30|Z|31|1|32]]|A|$]]|$1|1A|3|1B|5|6|7|33|8|@]|9|@]|A|$]]|$1|1C|3|1D|5|6|7|34|8|@$Y|35|Z|36|10|11]|$Y|37|Z|38|10|11]]|9|@]|A|$]]|$1|1E|3|1F|5|F|7|39|8|@]|9|@]|A|$G|H]]|$1|1G|3|1H|5|6|7|3A|8|@$Y|3B|Z|3C|10|11]|$Y|3D|Z|3E|10|11]]|9|@]|A|$]]|$1|1I|3|-4|5|6|7|3F|8|@]|9|@]|A|$]]|$1|1J|3|1K|5|1L|7|3G|8|@$Y|3H|Z|3I|10|1M]]|9|@]|A|$]]|$1|1N|3|-4|5|6|7|3J|8|@]|9|@]|A|$]]|$1|1O|3|-4|5|6|7|3K|8|@]|9|@]|A|$]]|$1|1P|3|1Q|5|6|7|3L|8|@]|9|@$Y|3M|Z|3N|1|3O]]|A|$]]|$1|1R|3|-4|5|6|7|3P|8|@]|9|@]|A|$]]|$1|1S|3|1T|5|1L|7|3Q|8|@$Y|3R|Z|3S|10|11]]|9|@]|A|$]]|$1|1U|3|-4|5|6|7|3T|8|@]|9|@]|A|$]]|$1|1V|3|-4|5|6|7|3U|8|@]|9|@]|A|$]]]|1W|$1X|$5|1Y|1Z|20|A|$21|22]]|23|$5|1Y|1Z|20|A|$21|24]]|25|$5|1Y|1Z|20|A|$21|26]]|27|$5|1Y|1Z|20|A|$21|28]]]]

<h2>Configuring credential.helper</h2>
On OS X (now macOS), run this in Terminal:
<pre><code>git config --global credential.helper osxkeychain
</code></pre>
It enables Git to use file Keychain.app to store username and password and to retrieve the passphrase to your private SSH key from the keychain.
For Windows use:
<pre><code>git config --global credential.helper wincred
</code></pre>
For Linux use:
<pre><code>git config --global credential.helper cache // If you want to cache the credentials for some time (default 15 minutes)
</code></pre>
OR
<pre><code>git config --global credential.helper store // if you want to store the credentials for ever (considered unsafe)
</code></pre>
Note: The first method will cache the credentials in memory, whereas the second will store them in <code>~/.git-credentials</code> in plain text format.
Check <a href="https://www.tecmint.com/fix-git-user-credentials-for-https/" rel="noreferrer">here</a> for more info about Linux method. 
Check <a href="https://docs.github.com/en/free-pro-team@latest/github/using-git/caching-your-github-credentials-in-git" rel="noreferrer">here</a> for more info about all three.
<h2>Troubleshooting</h2>
If the Git credential helper is configured correctly macOS saves the passphrase in the keychain. Sometimes the <a href="https://apple.stackexchange.com/questions/18458/password-dialog-appears-when-ssh-private-key-permissions-are-set-to-0600/139522#139522">connection between SSH and the passphrases stored in the keychain</a> can break. Run <code>ssh-add -K</code> or <code>ssh-add ~/.ssh/id_rsa</code> to add the key to keychain again.
<h2>macOS v10.12 (Sierra) changes to ssh</h2>
For macOS v10.12 (Sierra), <code>ssh-add -K</code> needs to be run after every reboot. To avoid this, create <code>~/.ssh/config</code> with this content.
<pre><code>Host *
 AddKeysToAgent yes
 UseKeychain yes
 IdentityFile ~/.ssh/id_rsa
</code></pre>
From the <code>ssh_config</code> <code>man</code> page on 10.12.2:
<blockquote>
UseKeychain
</blockquote>
<blockquote>
On macOS, specifies whether the system should search for passphrases in the user's keychain when attempting to use a particular key. When the passphrase is provided by the user, this option also specifies whether the passphrase should be stored into the keychain once it has been verified to be correct. The argument must be 'yes' or 'no'. The default is 'no'.
</blockquote>
Apple has added <a href="https://developer.apple.com/library/content/technotes/tn2449/_index.html" rel="noreferrer">Technote 2449</a> which explains what happened.
<blockquote>
Prior to macOS Sierra, <code>ssh</code> would present a dialog asking for your passphrase and would offer the option to store it into the keychain. This UI was deprecated some time ago and has been removed.
</blockquote>

blocks|key|4785543|text|我认为你已经解决了你的问题，但是我在这里看不到对我有帮助的解决方案，所以它就在这里。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4785544|在终端中键入：|4785545|echo+""+>+~/.ssh/known_hosts|code-block|syntax|javascript|4785546|这将清空您的known_hosts文件，您将不得不添加您使用和连接到的每个主机，但它解决了问题。|offset|length|style|CODE|4785547|entityMap^0|0|0|0|6|B|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|R|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|S|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|T|8|@$K|U|L|V|M|N]]|9|@]|A|$]]|$1|O|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|P|$]]

I figure you fixed your problem, but I don't see the solution here that helped me, so here it is.

Type in terminal:

<pre><code>echo "" &gt; ~/.ssh/known_hosts
</code></pre>

That will empty your <code>known_hosts</code> file, and you'll have to add every host you used and have connected to, but it solved the problem.

blocks|key|4785567|text|使用:将github.com替换为适当的主机名|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4785568|git+remote+set-url+origin+git@github.com:user/repo.git|code-block|syntax|javascript|4785569|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

Use this: Replace github.com with the appropriate hostname

<pre><code>git remote set-url origin git@github.com:user/repo.git
</code></pre>

blocks|key|2888183|text|我同意"codehugger“，并且使用"orkoden”的指令对我有效-在NetBeans+7.3上-当你右击文件并选择上下文菜单-推送-一个‘推送到远程’窗口打开-这里有两个选项：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2888184|2888185|origin:https://github.com/myaccount/myproject.git/|ordered-list-item|offset|length|style|CODE|2888186|https://github.com/myaccount/myproject.git/|2888187|2888188|正如您所看到的，不同之处在于URL中的原始参数-您不想选择此选项(1)，您希望选中选项(2)，这对我来说很好。|2888189|entityMap^0|0|0|0|1E|0|0|17|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|R|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|S|8|@$F|T|G|U|H|I]]|9|@]|A|$]]|$1|J|3|K|5|E|7|V|8|@$F|W|G|X|H|I]]|9|@]|A|$]]|$1|L|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|Z|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|10|8|@]|9|@]|A|$]]]|P|$]]

I agree with "codehugger" and using the instruction of "orkoden" it worked for me - on NetBeans 7.3 - when you right-click on the file and select context menu - push - a 'push to remote' window opened - there are two options here:

<ol>
<li><code>origin:https://github.com/myaccount/myproject.git/</code></li>
<li><code>https://github.com/myaccount/myproject.git/</code></li>
</ol>

As you can see, the difference is the origin parameter in the URL - you do not want to choose this option (1) you want to check option (2), and that works just fine for me.

blocks|key|676282|text|在Windows和GitHub上使用SSH推送/拉入的Git指南：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|676283|676284|下载并安装putty+|ordered-list-item|676285|设置环境变量'GIT_SSH‘=+'path\to\plink.exe’(在已安装的putty文件夹中)-要使环境变量生效(不能仅重新启动命令提示符)，请运行very+important!!!|676286|Restart+|offset|length|style|BOLD|676287|运行puttygen.exe以生成新密钥，将公钥复制到启动站点并将这个新私钥保存在磁盘上的安全位置(最好不要使用Dropbox)|676288|Run+github.co|676289|Quickly，并通过pageant运行"shell:startup".|676290|Make+GitHub+|676291|GitHub+to+github.co|676292|Quickly|676293|+to+Dropbox)|676294|Run启动文件夹。在启动文件夹中创建一个快捷方式，语法为“"path\to\privatekey"|676295|We”，不需要在repositories|676296|Very的.git/config中设置'puttykeyfile‘。重要的是，使用的是path\to\pageant.exe的“克隆URL”，而不是HTTPS.|676297|676298|entityMap|0|LINK|mutability|MUTABLE|url|http://en.wikipedia.org/wiki/Dropbox_%2528service%2529|1|http://en.wikipedia.org/wiki/Dropbox_%2528service%2529^0|0|0|0|0|0|8|0|0|1S|1K|7|0|0|0|D|0|0|10|0|0|C|0|0|J|0|0|7|0|0|C|4|7|1|0|0|1D|0|0|K|0|0|28|0|0^^$0|@$1|2|3|4|5|6|7|1I|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|1J|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|1K|8|@]|9|@]|A|$]]|$1|F|3|G|5|E|7|1L|8|@]|9|@]|A|$]]|$1|H|3|I|5|E|7|1M|8|@$J|1N|K|1O|L|M]]|9|@]|A|$]]|$1|N|3|O|5|E|7|1P|8|@$J|1Q|K|1R|L|M]]|9|@$J|1S|K|1T|1|1U]]|A|$]]|$1|P|3|Q|5|E|7|1V|8|@$J|1W|K|1X|L|M]]|9|@]|A|$]]|$1|R|3|S|5|E|7|1Y|8|@$J|1Z|K|20|L|M]]|9|@]|A|$]]|$1|T|3|U|5|E|7|21|8|@$J|22|K|23|L|M]]|9|@]|A|$]]|$1|V|3|W|5|E|7|24|8|@$J|25|K|26|L|M]]|9|@]|A|$]]|$1|X|3|Y|5|E|7|27|8|@$J|28|K|29|L|M]]|9|@]|A|$]]|$1|Z|3|10|5|E|7|2A|8|@$J|2B|K|2C|L|M]]|9|@$J|2D|K|2E|1|2F]]|A|$]]|$1|11|3|12|5|E|7|2G|8|@$J|2H|K|2I|L|M]]|9|@]|A|$]]|$1|13|3|14|5|E|7|2J|8|@$J|2K|K|2L|L|M]]|9|@]|A|$]]|$1|15|3|16|5|E|7|2M|8|@$J|2N|K|2O|L|M]]|9|@]|A|$]]|$1|17|3|-4|5|6|7|2P|8|@]|9|@]|A|$]]|$1|18|3|-4|5|6|7|2Q|8|@]|9|@]|A|$]]]|19|$1A|$5|1B|1C|1D|A|$1E|1F]]|1G|$5|1B|1C|1D|A|$1E|1H]]]]

Guide to Git on Windows and GitHub using SSH to push/pull: <a href="http://nathanj.github.io/gitguide/tour.html" rel="nofollow noreferrer">An Illustrated Guide to Git on Windows</a>

<ol>
<li>Download and install PuTTY</li>
<li>Set environment variable 'GIT_SSH' = 'path\to\plink.exe' (in installed putty folder) - very important!!!</li>
<li>Restart Windows Explorer for environment variables to take effect (cannot only restart command prompt)</li>
<li>Run puttygen.exe to generate new key, copy the public key to the GitHub site</li>
<li>Save this new private key somewhere safe on the disk (preferable not <a href="http://en.wikipedia.org/wiki/Dropbox_%28service%29" rel="nofollow noreferrer">Dropbox</a>)</li>
<li>Run putty.exe and connect SSH to github.co</li>
<li>Quickly get to startup folder by running "shell:startup".</li>
<li>Make your private key startup with Windows via pageant. Create a shortcut in Startup folder with syntax "path\to\pageant.exe" "path\to\privatekey"</li>
<li>We do not need to set the 'puttykeyfile' setting inside .git/config of our repositories</li>
<li>Very important is that the "SSH clone URL" of GitHub is used and not HTTPS.</li>
</ol>

blocks|key|673793|text|orkoden关于在您的终端中使用带有Git的密钥链的回答是不完整的，并引发了错误。要将在终端中输入的用户名和密码保存到您的钥匙链中，您必须执行以下操作：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|673794|curl+http://github-media-downloads.s3.amazonaws.com/osx/git-credential-osxkeychain+-o+git-credential-osxkeychain
sudo+mv+git-credential-osxkeychain+/usr/local/bin
sudo+chmod+u%2Bx+/usr/local/bin/git-credential-osxkeychain|code-block|syntax|javascript|673795|然后输入|673796|git+config+--global+credential.helper+osxkeychain|673797|如果您在使用curl之前已经使用Git配置完成了这一部分，这是没有问题的；它将会工作。|673798|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Q|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|R|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|S|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

orkoden's answer on using the keychain with Git in your terminal was incomplete and raises errors. This is what you have to do to save the username and password you enter in the the terminal in your keychain:

<pre><code>curl http://github-media-downloads.s3.amazonaws.com/osx/git-credential-osxkeychain -o git-credential-osxkeychain
sudo mv git-credential-osxkeychain /usr/local/bin
sudo chmod u+x /usr/local/bin/git-credential-osxkeychain
</code></pre>

Then enter

<pre><code>git config --global credential.helper osxkeychain
</code></pre>

If you have already done the part with Git configuration before the curl stuff, it's no problem; it'll work.

blocks|key|676333|text|正如其他人所说，你可以安装一个密码缓存助手。我主要只是想发布其他平台的链接，而不仅仅是Mac。我正在运行Linux服务器，这很有帮助：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|676334|对于Mac：|676335|git+credential-osxkeychain|code-block|syntax|javascript|676336|Windows：|676337|git+config+--global+credential.helper+wincred|676338|Linux：|676339|git+config+--global+credential.helper+cache
git+config+--global+credential.helper+'cache+--timeout=3600'
#+Set+the+cache+to+timeout+after+1+hour+(setting+is+in+seconds)|676340|entityMap^0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|T|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|U|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|V|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|W|8|@]|9|@]|A|$G|H]]|$1|M|3|N|5|6|7|X|8|@]|9|@]|A|$]]|$1|O|3|P|5|F|7|Y|8|@]|9|@]|A|$G|H]]|$1|Q|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|R|$]]

As others have said, you can install a password cache helper. I mostly just wanted to post the link for other platforms, and not just Mac. I'm running a Linux server and this was helpful: <a href="https://help.github.com/articles/caching-your-github-password-in-git/#platform-linux" rel="noreferrer">Caching your GitHub password in Git</a>

For Mac:

<pre><code>git credential-osxkeychain
</code></pre>

Windows:

<pre><code>git config --global credential.helper wincred
</code></pre>

Linux:

<pre><code>git config --global credential.helper cache
git config --global credential.helper 'cache --timeout=3600'
# Set the cache to timeout after 1 hour (setting is in seconds)
</code></pre>

blocks|key|676400|text|在用于Git+1.7.9%2B的Windows中，在命令提示符下运行以下命令，以在文本编辑器中打开配置文件：|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|676401|git+config+--global+--edit|code-block|syntax|javascript|676402|然后在文件中，添加以下块(如果不存在)或相应地对其进行编辑：|676403|[credential+"https://giturl.com"]
username+=+<user+id>
helper+=+wincred|676404|保存并关闭该文件。完成上述更改后，您只需提供一次凭据。|676405|entityMap^0|3|A|E|7|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@$9|T|A|U|B|C]|$9|V|A|W|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|X|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|Y|8|@]|D|@]|E|$]]|$1|M|3|N|5|H|7|Z|8|@]|D|@]|E|$I|J]]|$1|O|3|P|5|6|7|10|8|@]|D|@]|E|$]]|$1|Q|3|-4|5|6|7|11|8|@]|D|@]|E|$]]]|R|$]]

In Windows for Git 1.7.9+, run the following command on the command prompt to open the configuration file in a text editor:
<pre><code>git config --global --edit
</code></pre>
Then in the file, add the following block if not present or edit it accordingly:
<pre><code>[credential &quot;https://giturl.com&quot;]
username = &lt;user id&gt;
helper = wincred
</code></pre>
Save and close the file. You will need to provide the credentials only once after the above change.

blocks|key|4503729|text|步骤1:检查当前配置|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4503730|cat+.git/config|code-block|syntax|javascript|4503731|您将获得：|4503732|[core]
++++repositoryformatversion+=+0
++++filemode+=+true
++++bare+=+false
++++logallrefupdates+=+true
++++ignorecase+=+true
++++precomposeunicode+=+true
[remote+"origin"]
++++url+=+https://github.com/path_to_your_git.git
++++fetch+=+%2Brefs/heads/*:refs/remotes/origin/*
[user]
++++name+=+your_username
++++email+=+your_email
[branch+"master-staging"]
++++remote+=+origin
++++merge+=+refs/heads/master-staging|4503733|步骤2:删除您的远程源|4503734|git+remote+rm+origin|4503735|步骤3:添加您的用户名和密码的远程源站|4503736|git+remote+add+origin+https://your_git_username:your_git_password@github.com/path_to_your_git.git|4503737|entityMap^0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|V|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|W|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|X|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|Y|8|@]|9|@]|A|$]]|$1|M|3|N|5|D|7|Z|8|@]|9|@]|A|$E|F]]|$1|O|3|P|5|6|7|10|8|@]|9|@]|A|$]]|$1|Q|3|R|5|D|7|11|8|@]|9|@]|A|$E|F]]|$1|S|3|-4|5|6|7|12|8|@]|9|@]|A|$]]]|T|$]]

Step 1: check your current configuration

<pre><code>cat .git/config
</code></pre>

You will get: 

<pre><code>[core]
 repositoryformatversion = 0
 filemode = true
 bare = false
 logallrefupdates = true
 ignorecase = true
 precomposeunicode = true
[remote "origin"]
 url = https://github.com/path_to_your_git.git
 fetch = +refs/heads/*:refs/remotes/origin/*
[user]
 name = your_username
 email = your_email
[branch "master-staging"]
 remote = origin
 merge = refs/heads/master-staging
</code></pre>

Step 2: remove your remote origin

<pre><code>git remote rm origin
</code></pre>

Step 3: add remote origin back with your username and password

<pre><code>git remote add origin https://your_git_username:your_git_password@github.com/path_to_your_git.git
</code></pre>

blocks|key|2888445|text|正如static_rtti上面所说的，更改|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2888446|https://github.com/username/repo.git
git://github.com/username/repo.git|code-block|syntax|javascript|2888447|至|2888448|ssh://git@github.com/username/repo.git|2888449|我自己将.git/+https文件中的配置更改为ssh，但它仍然不起作用。然后，我看到您必须将github.com更改为git@github.com。获取实际正确URL的一个好方法是转到您的项目页面并单击以下内容：|offset|length|style|CODE|2888450|Change+HTTPS+to+SSH+to+get+the+right+URL|2888451|然后将此URL添加到配置文件中。|2888452|entityMap|0|LINK|mutability|MUTABLE|url|https://i.stack.imgur.com/HS1ua.png^0|0|0|0|0|A|5|O|3|1B|A|1O|E|0|0|14|0|0|0^^$0|@$1|2|3|4|5|6|7|12|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|13|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|14|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|15|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|16|8|@$M|17|N|18|O|P]|$M|19|N|1A|O|P]|$M|1B|N|1C|O|P]|$M|1D|N|1E|O|P]]|9|@]|A|$]]|$1|Q|3|R|5|6|7|1F|8|@]|9|@$M|1G|N|1H|1|1I]]|A|$]]|$1|S|3|T|5|6|7|1J|8|@]|9|@]|A|$]]|$1|U|3|-4|5|6|7|1K|8|@]|9|@]|A|$]]]|V|$W|$5|X|Y|Z|A|$10|11]]]]

As static_rtti said above, change

<pre><code>https://github.com/username/repo.git
git://github.com/username/repo.git
</code></pre>

to

<pre><code>ssh://git@github.com/username/repo.git
</code></pre>

I myself changed the <code>https</code> in the .git/config file to <code>ssh</code>, but it still wasn't working. Then I saw that you must change <code>github.com</code> to <code>git@github.com</code>. A good way to get the actual correct URL is to go to your project page and click this:

<a href="https://i.stack.imgur.com/HS1ua.png" rel="nofollow noreferrer">Change HTTPS to SSH to get the right URL</a>

Then add this URL to the configuration file.

blocks|key|673876|text|根据您的配置，有不同类型的身份验证。下面是一些例子：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|673877|673878|git+credential-osxkeychain.|ordered-list-item|offset|length|style|CODE|673879|673880|如果您的凭据无效，请通过以下方式将其删除：|673881|git凭据-osxkeychain擦除|673882|或者：|673883|printf+"protocol=https\nhost=github.com\n“%7C+git凭据-osxkeychain擦除|673884|这样Git就不会再向你索要密钥链权限了。然后重新配置它。|673885|请参阅：Updating+credentials+from+the+OS+X+Keychain+at+GitHub|673886|Your+SSH+RSA+key。|unordered-list-item|673887|673888|为此，您需要将您的SSH密钥与您添加的密钥进行比较，如果您使用的是正确的身份，请通过ssh-add+-L/ssh-add+-l检查。|673889|您的HTTPS身份验证(如果您使用的是https而不是ssh协议)。|673890|673891|使用~/.netrc+(Windows上的%25HOME%25/_netrc)提供您的凭据，例如|673892|机器stash1.mycompany.com登录myusername密码mypassword|673893|了解更多信息:堆栈的Syncing+with+GitHub和Overflow。|673894|entityMap|0|LINK|mutability|MUTABLE|url|https://help.github.com/articles/updating-credentials-from-the-osx-keychain/|1|https://stackoverflow.com/q/5377703/55075^0|0|0|0|Q|0|0|0|0|0|0|0|4|17|0|0|0|0|16|A|1H|A|0|J|5|R|3|0|0|2|8|L|D|0|0|A|J|1|0^^$0|@$1|2|3|4|5|6|7|1L|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|1M|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|1N|8|@$F|1O|G|1P|H|I]]|9|@]|A|$]]|$1|J|3|-4|5|6|7|1Q|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|1R|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|1S|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|1T|8|@]|9|@]|A|$]]|$1|Q|3|R|5|6|7|1U|8|@]|9|@]|A|$]]|$1|S|3|T|5|6|7|1V|8|@]|9|@]|A|$]]|$1|U|3|V|5|6|7|1W|8|@]|9|@$F|1X|G|1Y|1|1Z]]|A|$]]|$1|W|3|X|5|Y|7|20|8|@]|9|@]|A|$]]|$1|Z|3|-4|5|6|7|21|8|@]|9|@]|A|$]]|$1|10|3|11|5|6|7|22|8|@$F|23|G|24|H|I]|$F|25|G|26|H|I]]|9|@]|A|$]]|$1|12|3|13|5|Y|7|27|8|@$F|28|G|29|H|I]|$F|2A|G|2B|H|I]]|9|@]|A|$]]|$1|14|3|-4|5|6|7|2C|8|@]|9|@]|A|$]]|$1|15|3|16|5|6|7|2D|8|@$F|2E|G|2F|H|I]|$F|2G|G|2H|H|I]]|9|@]|A|$]]|$1|17|3|18|5|6|7|2I|8|@]|9|@]|A|$]]|$1|19|3|1A|5|6|7|2J|8|@]|9|@$F|2K|G|2L|1|2M]]|A|$]]|$1|1B|3|-4|5|6|7|2N|8|@]|9|@]|A|$]]]|1C|$1D|$5|1E|1F|1G|A|$1H|1I]]|1J|$5|1E|1F|1G|A|$1H|1K]]]]

There are different kind of authentications depending on your configuration. Here are a few:

<ol>
<li><code>git credential-osxkeychain</code>.

If your credential is invalid, remove it by:

<pre><code> git credential-osxkeychain erase
</code></pre>

or:

<pre><code> printf "protocol=https\nhost=github.com\n" | git credential-osxkeychain erase
</code></pre>

So Git won't ask you for the keychain permission again. Then configure it again.

See: <a href="https://help.github.com/articles/updating-credentials-from-the-osx-keychain/" rel="nofollow noreferrer">Updating credentials from the OS X Keychain</a> at GitHub</li>
<li>Your SSH RSA key.

For this, you need to compare your SSH key with what you've added, check by <code>ssh-add -L</code>/<code>ssh-add -l</code> if you're using the right identity.</li>
<li>Your HTTPS authentication (if you're using <code>https</code> instead of <code>ssh</code> protocol).

Use <code>~/.netrc</code> (<code>%HOME%/_netrc</code> on Windows), to provide your credentials, e.g.

<pre><code> machine stash1.mycompany.com
 login myusername
 password mypassword
</code></pre></li>
</ol>

Learn more: <a href="https://stackoverflow.com/q/5377703/55075">Syncing with GitHub</a> at Stack&nbsp;Overflow.

blocks|key|2888532|text|在GitHub中使用密钥之前，请按照教程中的步骤进行操作|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2888533|$+ssh+-T+git@github.com
#+Attempts+to+ssh+to+GitHub|code-block|syntax|javascript|2888534|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

Before you can use your key with GitHub, follow this step in the tutorial, <a href="https://help.github.com/articles/testing-your-ssh-connection/" rel="nofollow noreferrer">Testing your SSH connection</a>:

<pre class="lang-sh prettyprint-override"><code>$ ssh -T git@github.com
# Attempts to ssh to GitHub
</code></pre>

blocks|key|673916|text|当我升级到macOS+v10.12+(塞拉)时，这种情况就发生在我身上。看起来SSH代理在升级时被清除了。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|673917|$+ssh-add+-L
The+agent+has+no+identities.|code-block|syntax|javascript|673918|只需运行ssh-add即可找到我现有的身份。我输入了密码，可以再试一次了。|offset|length|style|CODE|673919|entityMap^0|0|0|4|7|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Q|8|@$I|R|J|S|K|L]]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

This happened to me when I upgraded to macOS v10.12 (Sierra). Looks like the SSH agent got cleared upon upgrade.

<pre><code>$ ssh-add -L
The agent has no identities.
</code></pre>

Simply running <code>ssh-add</code> located my existing identity. I entered the password and was good to go again.

blocks|key|2888605|text|git+config+credential.helper+store|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|2888606|注意:虽然这很方便，但Git将以明文形式将您的凭据存储在项目目录下的本地文件(.git-+credentials+)中(请参阅下面的"home“目录)。如果您不喜欢这样，请删除此文件并切换到使用缓存选项。|unstyled|2888607|如果您希望Git在每次需要连接到远程存储库时都恢复向您询问凭据，您可以运行以下命令：|2888608|git+config+--unset+credential.helper|2888609|要将密码存储在%25HOME%25目录中的.git-credentials中，而不是存储在project目录中:使用--global标志|2888610|git+config+--global+credential.helper+store|2888611|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$B|C]]|$1|D|3|E|5|F|7|R|8|@]|9|@]|A|$]]|$1|G|3|H|5|F|7|S|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|T|8|@]|9|@]|A|$B|C]]|$1|K|3|L|5|F|7|U|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|V|8|@]|9|@]|A|$B|C]]|$1|O|3|-4|5|F|7|W|8|@]|9|@]|A|$]]]|P|$]]

<pre><code>git config credential.helper store
</code></pre>

Note: While this is convenient, Git will store your credentials in clear text in a local file (.git-credentials) under your project directory (see below for the "home" directory). If you don't like this, delete this file and switch to using the cache option.

If you want Git to resume to asking you for credentials every time it needs to connect to the remote repository, you can run this command:

<pre><code>git config --unset credential.helper
</code></pre>

To store the passwords in .git-credentials in your %HOME% directory as opposed to the project directory: use the --global flag

<pre><code>git config --global credential.helper store
</code></pre>

blocks|key|2888675|text|还要看看是谁在向你索要密码。是Git还是你的SSH代理？|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2888676|在我的例子中，每次我执行git+pull时，它都会问我：|offset|length|style|CODE|2888677|Enter+passphrase+for+key+'/work/username/.ssh/id_rsa':|2888678|所以我以为是Git要密码。因此，我一直在寻找解决方案，后来才意识到我的SSH代理已经关闭。这可以使用eval+$(ssh-agent)和ssh-add作为给定的here.来修复|2888679|我还粘贴了下面的一小段代码，您可以将其添加到您的~/.bashrc文件(或等效文件)中，以确保在您登录时启动了您的SSH代理。|2888680|无论如何，这是我犯下的一个非常愚蠢的错误，但在这里张贴它，以防有人像我一样，节省了一些时间来攻击错误的树。|2888681|#+Start+the+ssh-agent
function+start_agent+{
++++echo+"Initializing+new+SSH+agent..."

++++#+Spawn+ssh-agent
++++/usr/bin/ssh-agent+%7C+sed+'s/%5Eecho/#echo/'+>+${SSH_ENV}
++++echo+succeeded
++++chmod+600+${SSH_ENV}
++++.+${SSH_ENV}+>+/dev/null
++++/usr/bin/ssh-add
}

if+[+-f+"${SSH_ENV}"+];+then
+++++.+${SSH_ENV}+>+/dev/null
+++++ps+-ef+%7C+grep+${SSH_AGENT_PID}+%7C+grep+ssh-agent$+>+/dev/null+%7C%7C+{
++++++++start_agent;
++++}
else
++++start_agent;
fi|code-block|syntax|javascript|2888682|entityMap|0|LINK|mutability|MUTABLE|url|https://unix.stackexchange.com/questions/12195/how-to-avoid-being-asked-passphrase-each-time-i-push-to-bitbucket^0|0|C|8|0|0|1I|0|1E|H|1W|7|28|5|0|0|O|9|0|0|0^^$0|@$1|2|3|4|5|6|7|12|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|13|8|@$D|14|E|15|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|16|8|@$D|17|E|18|F|G]]|9|@]|A|$]]|$1|J|3|K|5|6|7|19|8|@$D|1A|E|1B|F|G]|$D|1C|E|1D|F|G]]|9|@$D|1E|E|1F|1|1G]]|A|$]]|$1|L|3|M|5|6|7|1H|8|@$D|1I|E|1J|F|G]]|9|@]|A|$]]|$1|N|3|O|5|6|7|1K|8|@]|9|@]|A|$]]|$1|P|3|Q|5|R|7|1L|8|@]|9|@]|A|$S|T]]|$1|U|3|-4|5|6|7|1M|8|@]|9|@]|A|$]]]|V|$W|$5|X|Y|Z|A|$10|11]]]]

Also look for who is asking you for the passphrase. Is it Git or your SSH agent?

In my case, every time I did <code>git pull</code> it was asking me:

<code>Enter passphrase for key '/work/username/.ssh/id_rsa':</code>

So I assumed it was Git asking for a passphrase. So I kept hunting for solutions, only to realize later that my SSH agent had shut down. Which can be fixed using <code>eval $(ssh-agent)</code> and <code>ssh-add</code> as given <a href="https://unix.stackexchange.com/questions/12195/how-to-avoid-being-asked-passphrase-each-time-i-push-to-bitbucket">here.</a>

Also am pasting below a little snippet you can add to your <code>~/.bashrc</code> file (or the equivalent) to ensure that your SSH agent is started on your login.

In any case this was a pretty silly mistake I made, but posting it here, just in case it helps someone save some time from barking up the wrong tree, like I did.

<pre><code># Start the ssh-agent
function start_agent {
 echo "Initializing new SSH agent..."

 # Spawn ssh-agent
 /usr/bin/ssh-agent | sed 's/^echo/#echo/' &gt; ${SSH_ENV}
 echo succeeded
 chmod 600 ${SSH_ENV}
 . ${SSH_ENV} &gt; /dev/null
 /usr/bin/ssh-add
}

if [ -f "${SSH_ENV}" ]; then
 . ${SSH_ENV} &gt; /dev/null
 ps -ef | grep ${SSH_AGENT_PID} | grep ssh-agent$ &gt; /dev/null || {
 start_agent;
 }
else
 start_agent;
fi

</code></pre>

blocks|key|4503999|text|使用以下命令增加超时时间，以便您可以重新键入密码一段时间|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4504000|git+config+--global+credential.helper+'cache+--timeout+3600'|code-block|syntax|javascript|4504001|我把它用在了Bitbucket和GitHub上，两者都适用。你唯一需要做的就是在几秒钟内完成3600。将其增加到您想要的任何程度。我把它改成了259200，大概是30天。这样，我每隔30天左右就会重新输入我的密码。|offset|length|style|CODE|4504002|entityMap^0|0|0|1A|4|1Z|6|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Q|8|@$I|R|J|S|K|L]|$I|T|J|U|K|L]]|9|@]|A|$]]|$1|M|3|-4|5|6|7|V|8|@]|9|@]|A|$]]]|N|$]]

Use the following command to increase the timeout period so that you could retype password for a while

<pre><code>git config --global credential.helper 'cache --timeout 3600'
</code></pre>

I used it for Bitbucket and GitHub it works for both. The only thing you need to do is
<code>3600</code> is in seconds. Increase it to whatever extent you want. I changed it to <code>259200</code> which is about 30 days. This way I re-enter my password for every 30 days or so.

blocks|key|2888746|text|如果你使用的是Windows，而这突然开始在GitHub上发生，这可能是因为GitHub最近在2018-02-22发布了disabling+support+for+deprecated+cryptographic+algorithms，在这种情况下，解决方案很简单，要么下载并安装最新版本的完整Git+for+Windows，要么只下载Git+Credential+Manager+for+Windows。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2888747|entityMap|0|LINK|mutability|MUTABLE|url|https://githubengineering.com/crypto-removal-notice/|1|https://github.com/git-for-windows/git/releases|2|https://github.com/Microsoft/Git-Credential-Manager-for-Windows/releases^0|1O|1L|0|43|F|1|4O|Y|2|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@$A|Q|B|R|1|S]|$A|T|B|U|1|V]|$A|W|B|X|1|Y]]|C|$]]|$1|D|3|-4|5|6|7|Z|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]|L|$5|G|H|I|C|$J|M]]|N|$5|G|H|I|C|$J|O]]]]

If you're using Windows and this has suddenly started happening on out of the blue on GitHub, it's probably due to GitHub's recent <a href="https://githubengineering.com/crypto-removal-notice/" rel="nofollow noreferrer">disabling support for deprecated cryptographic algorithms</a> on 2018-02-22, in which case the solution is simply to download and install the latest version of either the full <a href="https://github.com/git-for-windows/git/releases" rel="nofollow noreferrer">Git for Windows</a> 
or just the <a href="https://github.com/Microsoft/Git-Credential-Manager-for-Windows/releases" rel="nofollow noreferrer">Git Credential Manager for Windows</a>.

blocks|key|674031|text|我觉得static_rtti提供的答案在某种意义上有点老生常谈。我不知道以前是否有这个功能，但Git工具现在提供了凭据存储。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|674032|缓存模式|offset|length|style|BOLD|674033|$+git+config+--global+credential.helper+cache|code-block|syntax|javascript|674034|使用缓存模式将凭证保存在内存中一段时间。所有密码都不会存储在磁盘上，它们会在15分钟后从缓存中清除。|674035|存储模式|674036|$+git+config+--global+credential.helper+'store+--file+~/.my-credentials'|674037|使用“存储”模式将凭据保存到磁盘上的纯文本文件中，凭据永远不会过期。|674038|我个人使用的是商店模式。我删除了我的存储库，克隆了它，然后必须输入我的凭据一次。|674039|参考：|674040|entityMap^0|0|0|4|0|0|0|0|4|0|0|0|7|4|0|0^^$0|@$1|2|3|4|5|6|7|10|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|11|8|@$D|12|E|13|F|G]]|9|@]|A|$]]|$1|H|3|I|5|J|7|14|8|@]|9|@]|A|$K|L]]|$1|M|3|N|5|6|7|15|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|16|8|@$D|17|E|18|F|G]]|9|@]|A|$]]|$1|Q|3|R|5|J|7|19|8|@]|9|@]|A|$K|L]]|$1|S|3|T|5|6|7|1A|8|@]|9|@]|A|$]]|$1|U|3|V|5|6|7|1B|8|@$D|1C|E|1D|F|G]]|9|@]|A|$]]|$1|W|3|X|5|6|7|1E|8|@]|9|@]|A|$]]|$1|Y|3|-4|5|6|7|1F|8|@]|9|@]|A|$]]]|Z|$]]

I feel like the answer provided by static_rtti is hacky in some sense. I don't know if this was available earlier, but Git tools now provide credential storage.

Cache Mode

<pre><code>$ git config --global credential.helper cache
</code></pre>

Use the “cache” mode to keep credentials in memory for a certain period of time. None of the passwords are ever stored on disk, and they are purged from the cache after 15 minutes.

Store Mode

<pre><code>$ git config --global credential.helper 'store --file ~/.my-credentials'
</code></pre>

Use the “store” mode to save the credentials to a plain-text file on disk, and they never expire. 

I personally used the store mode. I deleted my repository, cloned it, and then had to enter my credentials once. 

Reference: <a href="https://git-scm.com/book/en/v2/Git-Tools-Credential-Storage" rel="noreferrer">7.14 Git Tools - Credential Storage</a>

blocks|key|674049|text|如果每次您尝试与GitHub交互时，Git都会提示您输入用户名和密码，那么您可能正在使用存储库的HTTPS+clone+URL。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|674050|使用HTTPS远程URL有一些优点:它比SSH更容易设置，并且通常通过严格的防火墙和代理工作。但是，每次拉取或推送存储库时，它也会提示您输入GitHub凭据。|674051|您可以配置Git为您存储您的密码。用于的|674052|git+config+--global+credential.helper+wincred|code-block|syntax|javascript|674053|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|N|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|O|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|P|8|@]|9|@]|A|$I|J]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

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. For Windows:

<pre><code>git config --global credential.helper wincred
</code></pre>

blocks|key|2888829|text|在Windows+Subsystem+for+Linux+(WSL)上，这是我发现的唯一有效的解决方案：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2888830|eval+ssh-agent+;+ssh-add+~/.ssh/id_rsa|offset|length|style|CODE|2888831|这是一个没有在WSL中正确注册ssh-agent的问题。|2888832|entityMap^0|0|0|4|5|9|F|N|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@$D|N|E|O|F|G]|$D|P|E|Q|F|G]|$D|R|E|S|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|T|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|U|8|@]|9|@]|A|$]]]|K|$]]

On Windows Subsystem for Linux (WSL) this was the only solution that I found to work:

<code>eval</code> `ssh-agent` <code>; ssh-add ~/.ssh/id_rsa</code>

It was a problem with the ssh-agent not being properly registered in WSL.

blocks|key|4504136|text|如果您想stop+Git+from+always+asking您的GitHub存储库的登录凭据，这很容易做到。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|4504137|使用SSH代替HTTPS|4504138|您可以使用SSH而不是HTTPS更新源远程。“|4504139|git+remote+set-url+origin+git@github.com:username/your-repo.git|code-block|syntax|javascript|4504140|配置Git来存储您的密码和用户名|4504141|下面是如何让Git存储用户名和密码的方法：|4504142|git+config+--global+credential.helper+store|4504143|接下来，保存会话的用户名和密码：|4504144|git+config+--global+credential.helper+cache|4504145|entityMap|0|LINK|mutability|MUTABLE|url|https://www.techiediaries.com/git/stop-git-always-asking-for-username-and-password-when-using-https/^0|4|R|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|14|8|@]|9|@$A|15|B|16|1|17]]|C|$]]|$1|D|3|E|5|6|7|18|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|19|8|@]|9|@]|C|$]]|$1|H|3|I|5|J|7|1A|8|@]|9|@]|C|$K|L]]|$1|M|3|N|5|6|7|1B|8|@]|9|@]|C|$]]|$1|O|3|P|5|6|7|1C|8|@]|9|@]|C|$]]|$1|Q|3|R|5|J|7|1D|8|@]|9|@]|C|$K|L]]|$1|S|3|T|5|6|7|1E|8|@]|9|@]|C|$]]|$1|U|3|V|5|J|7|1F|8|@]|9|@]|C|$K|L]]|$1|W|3|-4|5|6|7|1G|8|@]|9|@]|C|$]]]|X|$Y|$5|Z|10|11|C|$12|13]]]]

If you want to <a href="https://www.techiediaries.com/git/stop-git-always-asking-for-username-and-password-when-using-https/" rel="noreferrer">stop Git from always asking</a> you for the login credentials of your GitHub repository this can be easily done.

<h2>Using SSH instead of HTTPS</h2>

You can update the origin remote using SSH instead of HTTPS"

<pre class="lang-sh prettyprint-override"><code>git remote set-url origin git@github.com:username/your-repo.git
</code></pre>

<h2>Configure Git to Store your Password and Username</h2>

Here’s how you can make Git store the username and password:

<pre class="lang-sh prettyprint-override"><code>git config --global credential.helper store
</code></pre>

Next, save the username and password for a session:

<pre class="lang-sh prettyprint-override"><code>git config --global credential.helper cache
</code></pre>

blocks|key|2888889|text|微软堆栈解决方案(Windows和Azure+DevOps)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2888890|首先打开.git/config文件，确保地址如下所示：|offset|length|style|CODE|2888891|protocol://something@url|code-block|syntax|javascript|2888892|例如，Azure+DevOps的.git/config：|2888893|[remote+"origin"]
++++url+=+https://mystore@dev.azure.com/mystore/myproject/
++++fetch+=+%2Brefs/heads/*:refs/remotes/origin/*|2888894|如果问题仍然存在，请打开Windows凭据管理器，单击名为Windows+的保险箱，然后删除所有与相关的凭据。|BOLD|2888895|现在，当你下次登录git时，它不会再消失了。|2888896|entityMap^0|0|4|B|0|0|0|0|T|8|1D|6|0|0|M|0^^$0|@$1|2|3|4|5|6|7|X|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Y|8|@$D|Z|E|10|F|G]]|9|@]|A|$]]|$1|H|3|I|5|J|7|11|8|@]|9|@]|A|$K|L]]|$1|M|3|N|5|6|7|12|8|@]|9|@]|A|$]]|$1|O|3|P|5|J|7|13|8|@]|9|@]|A|$K|L]]|$1|Q|3|R|5|6|7|14|8|@$D|15|E|16|F|S]|$D|17|E|18|F|S]]|9|@]|A|$]]|$1|T|3|U|5|6|7|19|8|@$D|1A|E|1B|F|S]]|9|@]|A|$]]|$1|V|3|-4|5|6|7|1C|8|@]|9|@]|A|$]]]|W|$]]

<h2>Microsoft Stack solution (Windows and Azure DevOps)</h2>

First open the <code>.git/config</code> file to make sure the address looks like: 

<pre><code>protocol://something@url
</code></pre>

E.g. .git/config for Azure DevOps:

<pre><code>[remote "origin"]
 url = https://mystore@dev.azure.com/mystore/myproject/
 fetch = +refs/heads/*:refs/remotes/origin/*
</code></pre>

If the problem still persists, open Windows Credential Manager, click on the safebox named Windows Credentials and remove all the git related credentials.

Now the next time you log into git, it won't go away anymore.

blocks|key|674112|text|运行macOS+Cataline10.15时，密钥链缓存方法对我不起作用。我想使用https://，而不是ssh|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|674113|以下是对我有效的方法：|674114|git+remote+rm+origin

git+remote+add+origin+https://your_git_username:your_git_password@github.com/path_to_your_git.git|code-block|syntax|javascript|674115|这在GitLab上也应该有效|674116|如果用户名包含电子邮件地址，请确保删除@email部分，否则将出现错误，声明为URL+using+bad/illegal+format+or+missing+URL。|674117|希望这能有所帮助！|674118|entityMap^0|15|8|1H|3|0|0|0|0|J|6|13|17|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@$9|V|A|W|B|C]|$9|X|A|Y|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|Z|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|10|8|@]|D|@]|E|$K|L]]|$1|M|3|N|5|6|7|11|8|@]|D|@]|E|$]]|$1|O|3|P|5|6|7|12|8|@$9|13|A|14|B|C]|$9|15|A|16|B|C]]|D|@]|E|$]]|$1|Q|3|R|5|6|7|17|8|@]|D|@]|E|$]]|$1|S|3|-4|5|6|7|18|8|@]|D|@]|E|$]]]|T|$]]

Running macOS Cataline 10.15, the keychain caching method was not working for me. And I wanted to use <code>https://</code> not <code>ssh</code> 

Here is what worked for me:

<pre><code>git remote rm origin

git remote add origin https://your_git_username:your_git_password@github.com/path_to_your_git.git
</code></pre>

This should work on GitLab too

Make sure if the username contains an email address, to remove the <code>@email</code> part or you'll get an error stating <code>URL using bad/illegal format or missing URL</code>.

Hope this helps!

blocks|key|4504275|text|如果您设置了SSH代理，您还可以将以下内容添加到您~/.gitconfig中，以强制git对所有GitHub存储库使用SSH，而不是HTTPS：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|4504276|[url+"ssh://git@github.com/"]
++++insteadOf+=+git://github.com/
++++insteadOf+=+https://github.com/|code-block|syntax|javascript|4504277|(如果您主要使用公共存储库，也可以使用pushInsteadOf而不是insteadOf，因为从公共存储库读取数据无需身份验证即可完成)。|4504278|entityMap^0|P|C|0|0|J|D|Z|9|0^^$0|@$1|2|3|4|5|6|7|O|8|@$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|R|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|S|8|@$9|T|A|U|B|C]|$9|V|A|W|B|C]]|D|@]|E|$]]|$1|M|3|-4|5|6|7|X|8|@]|D|@]|E|$]]]|N|$]]

If you have SSH agent set up, you can also add this to your <code>~/.gitconfig</code> to force git to use SSH for all GitHub repos rather than HTTPS:

<pre><code>[url "ssh://git@github.com/"]
 insteadOf = git://github.com/
 insteadOf = https://github.com/
</code></pre>

(If you're mostly working with public repos, you can also use <code>pushInsteadOf</code> rather than <code>insteadOf</code>, as reading from a public repo can be done without authentication).

blocks|key|4786531|text|我也有同样的问题。MacOS+Mojave+keychain不断要求提供密码短语。出于安全考虑，您的id_rsa应该使用密码进行加密。然后尝试将其添加到密钥链ssh-add+-K+~/.ssh/id_rsa中|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|4786532|如果您的密钥位于~/.ssh以外的其他文件夹中，请替换为正确的文件夹。|4786533|Keychain现在知道了您的ssh密钥，希望现在一切都能正常工作。|4786534|如果您仍然面临这个问题，请尝试|4786535|1.+brew+install+keychain

2.+echo+'/usr/local/bin/keychain+$HOME/.ssh/id_rsa'+>>+~/.bash_profile
+++echo+'source+$HOME/.keychain/$HOSTNAME-sh'+~/.bash_profile

3.+ssh-add+-K+~/.ssh/id_rsa|code-block|syntax|javascript|4786536|希望它现在可以工作了。|4786537|entityMap^0|27|O|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@$9|V|A|W|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|X|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|Y|8|@]|D|@]|E|$]]|$1|J|3|K|5|6|7|Z|8|@]|D|@]|E|$]]|$1|L|3|M|5|N|7|10|8|@]|D|@]|E|$O|P]]|$1|Q|3|R|5|6|7|11|8|@]|D|@]|E|$]]|$1|S|3|-4|5|6|7|12|8|@]|D|@]|E|$]]]|T|$]]

I had the same problem. MacOS Mojave keychain keeps asking for the passphrase. Your id_rsa should be encrypted with a passphrase for security.
Then try adding it to the keychain <code>ssh-add -K ~/.ssh/id_rsa</code>
If your key is in another folder than ~/.ssh then substitute with the correct folder.
Keychain now knows your ssh key, hopefully, all works now.
If you are still facing the issue then try
<pre><code>1. brew install keychain

2. echo '/usr/local/bin/keychain $HOME/.ssh/id_rsa' &gt;&gt; ~/.bash_profile
 echo 'source $HOME/.keychain/$HOSTNAME-sh' ~/.bash_profile

3. ssh-add -K ~/.ssh/id_rsa
</code></pre>
Hopefully, it should work now.

blocks|key|2889194|text|如果您使用的是https协议，Git会提示您输入密码。如果您使用ssh，它将使用您的私钥进行身份验证，而不是询问密码。(https://help.github.com/en/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account)|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2889195|以下是如何解决此问题的方法：|2889196|git+remote+-v|2889197|这将显示源的url。您将注意到此url中的https。(示例：https://github.com/PrestaShop/PrestaShop.git)|2889198|现在，您只需先将其删除，然后使用ssh添加url|2889199|git+remote+remove+origin|2889200|git+remote+add+origin+git@github.com:PrestaShop/PrestaShop.git|2889201|entityMap|0|LINK|mutability|MUTABLE|url|https://help.github.com/en/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account|1|https://github.com/PrestaShop/PrestaShop.git^0|7|5|W|3|1O|2U|0|0|0|0|D|0|L|5|V|18|1|0|G|3|0|0|O|0|0|1Q|0^^$0|@$1|2|3|4|5|6|7|11|8|@$9|12|A|13|B|C]|$9|14|A|15|B|C]]|D|@$9|16|A|17|1|18]]|E|$]]|$1|F|3|G|5|6|7|19|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|1A|8|@$9|1B|A|1C|B|C]]|D|@]|E|$]]|$1|J|3|K|5|6|7|1D|8|@$9|1E|A|1F|B|C]]|D|@$9|1G|A|1H|1|1I]]|E|$]]|$1|L|3|M|5|6|7|1J|8|@$9|1K|A|1L|B|C]]|D|@]|E|$]]|$1|N|3|O|5|6|7|1M|8|@$9|1N|A|1O|B|C]]|D|@]|E|$]]|$1|P|3|Q|5|6|7|1P|8|@$9|1Q|A|1R|B|C]]|D|@]|E|$]]|$1|R|3|-4|5|6|7|1S|8|@]|D|@]|E|$]]]|S|$T|$5|U|V|W|E|$X|Y]]|Z|$5|U|V|W|E|$X|10]]]]

Git will prompt you for a passowrd if you are using <code>https</code> protocol. If you use <code>ssh</code>, it will do the authentication using your private key instead of asking for password. (<a href="https://help.github.com/en/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account" rel="nofollow noreferrer">https://help.github.com/en/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account</a>)
Here is how to fix this:
<code>git remote -v</code>
This will show the url for origin. And you will notice <code>https</code> in this url. (Example : <a href="https://github.com/PrestaShop/PrestaShop.git" rel="nofollow noreferrer">https://github.com/PrestaShop/PrestaShop.git</a>)
Now, you will have to just remove this first and add the url with <code>ssh</code>
<code>git remote remove origin</code>
<code>git remote add origin git@github.com:PrestaShop/PrestaShop.git</code>

blocks|key|4786651|text|我有这个问题。一个repo每次都要求我输入凭证。我所有其他的推荐信都没有要求我的证书。它们甚至被设置为在相同的帐户凭据下使用HTTPS来跟踪GitLab，所以奇怪的是，除了一个之外，它们都工作得很好。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4786652|通过比较.git/config文件，我发现导致该问题的URL存在两个关键差异：|4786653|要求提供凭据：|4786654|https://gitlab.com/myaccount/myproject|code-block|syntax|javascript|4786655|不要求提供凭据：|4786656|https://myaccount@gitlab.com/myaccount/myproject.git+|4786657|因此，添加"myaccount@“和".git”解决了我的问题。|4786658|entityMap^0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|T|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|U|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|V|8|@]|9|@]|A|$I|J]]|$1|K|3|L|5|6|7|W|8|@]|9|@]|A|$]]|$1|M|3|N|5|H|7|X|8|@]|9|@]|A|$I|J]]|$1|O|3|P|5|6|7|Y|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|R|$]]

I had this issue. A repo was requiring me to input credentials every time. All my other repos were not asking for my credentials. They were even set up to track GitLab using HTTPS under the same account credentials, so it was weird that they all worked fine except one.
Comparing the .git/config files, I found that there were 2 key differences in the URLs which was causing the issue:
Does ask for credentials:
<pre><code>https://gitlab.com/myaccount/myproject
</code></pre>
Does not ask for credentials:
<pre><code>https://myaccount@gitlab.com/myaccount/myproject.git 
</code></pre>
So adding the &quot;myaccount@&quot; and &quot;.git&quot; resolved the issue in my case.

blocks|key|4504522|text|在我的例子中，当我尝试cherrypick+a+URL时，总是得到一个密码提示，如下所示：|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|4504523|git+fetch+http://username@gerrit-domainname/repositoryname+refs/changes/1/12345/1+&&+git+cherry-pick+FETCH_HEAD|code-block|syntax|javascript|4504524|当cherrypicked在不同的机器上运行时，这个URL工作得很好。然而，在我尝试使用正确的密码abc@12345进行cherrypick时，我会得到以下错误：|CODE|4504525|remote:+Unauthorized
remote:+Authentication+failed+for+http://username@gerrit-domainname++|4504526|在我的git配置文件中，远程URL如下：|4504527|url+=+ssh://gerrit-domainname:8080/wnc|4504528|解决方案：|4504529|我通过提供HTTP密码解决了身份验证失败的问题|4504530|我的gerrit帐户->设置->+HTTP密码。|4504531|HTTP密码类似于Th%2BIsAduMMy%2BPaSS%2BWordT%2BRY%2BYour%2BOwNPaSs，它与我的实际密码abc@12345有很大不同|4504532|注意：我的cherrpick网址以git+fetch+...开头，因此，此解决方案可能适用于签出/下载，网址以git+fetch+...开头|4504533|entityMap^0|B|A|0|0|1D|9|0|0|3|7|0|0|0|5|0|5|6|0|H|6|0|9|12|1K|9|0|0|2|1A|O|H|D|1J|D|0^^$0|@$1|2|3|4|5|6|7|15|8|@$9|16|A|17|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|18|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|19|8|@$9|1A|A|1B|B|M]]|D|@]|E|$]]|$1|N|3|O|5|H|7|1C|8|@]|D|@]|E|$I|J]]|$1|P|3|Q|5|6|7|1D|8|@$9|1E|A|1F|B|C]]|D|@]|E|$]]|$1|R|3|S|5|H|7|1G|8|@]|D|@]|E|$I|J]]|$1|T|3|U|5|6|7|1H|8|@$9|1I|A|1J|B|C]]|D|@]|E|$]]|$1|V|3|W|5|6|7|1K|8|@$9|1L|A|1M|B|C]]|D|@]|E|$]]|$1|X|3|Y|5|6|7|1N|8|@$9|1O|A|1P|B|C]]|D|@]|E|$]]|$1|Z|3|10|5|6|7|1Q|8|@$9|1R|A|1S|B|M]|$9|1T|A|1U|B|M]]|D|@]|E|$]]|$1|11|3|12|5|6|7|1V|8|@$9|1W|A|1X|B|C]|$9|1Y|A|1Z|B|C]|$9|20|A|21|B|M]|$9|22|A|23|B|M]]|D|@]|E|$]]|$1|13|3|-4|5|6|7|24|8|@]|D|@]|E|$]]]|14|$]]

In my case, I was always getting a password prompt when I tried to cherrypick a URL like below:
<pre><code>git fetch http://username@gerrit-domainname/repositoryname refs/changes/1/12345/1 &amp;&amp; git cherry-pick FETCH_HEAD
</code></pre>
This URL worked well when cherrypicked on a different machine. However, At my end when I try to cherrypick with correct password <code>abc@12345</code> I used to get below error:
<pre><code>remote: Unauthorized
remote: Authentication failed for http://username@gerrit-domainname 
</code></pre>
In my git config file the remote URL was like below:
<pre><code>url = ssh://gerrit-domainname:8080/wnc
</code></pre>
Solution: 
I resolved the authentication failure issue by providing the HTTP Password which I found at 
My gerrit account -&gt; Settings -&gt; HTTP Password.
The HTTP Password was something like <code>Th+IsAduMMy+PaSS+WordT+RY+Your+OwNPaSs</code> which was way different than my actual password <code>abc@12345</code>
Note: My URL to cherrpick starts with <code>git fetch ...</code> So, this solution might work on git checkout/download where the URL starts with <code>git fetch ...</code>

blocks|key|2889346|text|面临着同样的问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2889347|请确保您正确设置了远程源：|2889348|$git+remote+add+origin+master+"https://...git+"+|code-block|syntax|javascript|2889349|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|L|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|M|8|@]|9|@]|A|$G|H]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

Faced same kind of issue.
Please make sure you have properly set the remote origin:
<pre><code>$git remote add origin master &quot;https://...git &quot; 
</code></pre>

blocks|key|4504590|text|在windows计算机中:安装GitHub命令行界面|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4504591|choco+install+gh|code-block|syntax|javascript|4504592|然后运行命令：|4504593|gh+auth+login|4504594|并按照说明进行操作|4504595|此外，您还可以访问以下链接：|4504596|https://cli.github.com/manual/gh_auth_login|offset|length|4504597|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|0|0|0|0|0|17|0|0^^$0|@$1|2|3|4|5|6|7|Z|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|10|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|11|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|12|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|13|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|14|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|15|8|@]|9|@$Q|16|R|17|1|18]]|A|$]]|$1|S|3|-4|5|6|7|19|8|@]|9|@]|A|$]]]|T|$U|$5|V|W|X|A|$Y|P]]]]

In windows machine:
Install GitHub CLI
<pre><code>choco install gh
</code></pre>
Then run the command:
<pre><code>gh auth login
</code></pre>
and follow the Instruction
Also you can follow this link:
<a href="https://cli.github.com/manual/gh_auth_login" rel="nofollow noreferrer">https://cli.github.com/manual/gh_auth_login</a>

I've been using Git for a while now, but the constant requests for a password are starting to drive me up the wall.

I'm using Mac&nbsp;OS&nbsp;X and GitHub, and I set up Git and my SSH keys as instructed by GitHub's <a href="http://help.github.com/mac-set-up-git/" rel="noreferrer">Set Up Git page</a>. 

I've also added the github SSH key to my Mac&nbsp;OS&nbsp;X keychain, as mentioned on <a href="http://help.github.com/ssh-key-passphrases/" rel="noreferrer">GitHub's SSH key passphrases page</a>. My public key is registered with Git.

Nevertheless, every time I try to Git pull, I have to enter my username and password. Is there something other than an SSH key that I need to set up for this?

Git keeps prompting me for a password

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我使用Git已经有一段时间了，但不断有人要求我输入密码，这让我非常恼火。我使用的是Mac和GitHub，我按照GitHub的的指示设置了Git和我的SSH密钥。正如上提到的，我还将github SSH密钥添加到我的Mac-OS-X密钥链中。我的公钥是用Git注册的。然而，每次我尝试Git pull时，我都必须输入我的用...

问Git一直提示我输入密码
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Git一直提示我输入密码EN