有没有办法让 Bitbucket 在每次进行远程 Mercurial 操作时不询问我的密码？
对于我推送到的所有其他 Mercurial 存储库，我可以在 hgrc（实际上是 Mercurial.ini，因为我使用 Windows）中设置用户名和密码，以便在特定域中执行操作，并且 Mercurial 不会提示我进行身份验证信息。然而，即使进行了这些设置，Bitbucket总是要求我输入密码。
我的设置如下：
[auth]
bitbucket.prefix = bitbucket.org
bitbucket.username = myusername
bitbucket.password = mypassword
正如我所说，这些设置适用于我推送到的所有其他存储库。
With all other Mercurial repos that I push to, I can set my username and password in my hgrc (actually, Mercurial.ini since I'm using Windows) for doing operations at a particular domain, and Mercurial won't prompt me for auth info. However, even with these settings in place, Bitbucket always asks for my password.
My settings are as follows:
[auth]
bitbucket.prefix = bitbucket.org
bitbucket.username = myusername
bitbucket.password = mypassword
As I said, these settings work for all other repos I push to.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
事实证明，这里的问题是我使用了 Bitbucket 存储库页面上显示的存储库的 URL，其中包括 bitbucket 域名前面的用户名，因此它最终看起来像
https://[电子邮件受保护]/myusername/myrepo。显然，当以这种方式提供用户名时，它会忽略
[auth]部分中的内容。我刚刚更改了 hgrc 中存储库本地克隆的 URL，它就很好地获取了[auth]部分的内容。很抱歉没有在问题中包含此细节。
Turns out the issue here was that I was using the URL for the repository displayed on my Bitbucket repository's page, which includes the username in front of the bitbucket domain name, so it ended up looking like
https://[email protected]/myusername/myrepo.Apparently, when the username is provided in this way, it ignores what's in the
[auth]section. I just changed the URL in the hgrc for my local clone of the repo, and it picked up the[auth]section stuff just fine.Apologies for not including this detail in the question.
您使用的是 bitbucket 的 ssh:// URL 还是 https:// URL？ Bitbucket 两者都提供。如果是 ssh，您需要使用 ssh-agent 或类似的（ssh 不使用
[auth]部分）将密钥保留在内存中或切换到 https: URL。您也可以尝试添加bitbucket.schemes = http https以防万一，但如果您使用 https:// URL，则https的默认值应该没问题。另请注意，bitbucket 用户名区分大小写——这让我困扰了一段时间。如果这些都对您不起作用，请尝试使用
--debug打开调试，并查看是否有任何有帮助的消息。Are you using the ssh:// URLs for bitbucket or the https:// URLs? Bitbucket offers both. If it's ssh you need to use ssh-agent or similar (
[auth]sections aren't used by ssh) to keep a key in memory or switch to the https: URLs. You could also try addingbitbucket.schemes = http httpsjust in case, though if you're using the https:// URLs the default value ofhttpsshould be fine. Also be aware that bitbucket usernames are case sensitive -- that got me for awhile.If none of that's working for you try turning on debugging with
--debugand see if there are any messages that help.