-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mercurial keyring support #34
Comments
It is supported, I just tried and it works out-of-the-box. You can also try with something like this in your .hgrc: [auth]
bb.prefix = https://bitbucket.org/foo/
bb.username = foo
bb.password = foo_passwd |
Are we both talking about https://pypi.python.org/pypi/mercurial_keyring (support for KWallet, Gnome Keyring, OSX and Windows keyrings)? Doesn't look like your code is doing a Adding
Gets me to the point of |
All extensions get eventually loaded. You first push once with mercurial, and then then the rest of the time you can push in git. I tested it, it works fine. If there's a good reason we could turn on interactivity, or use git's keyring support. But I think for now the support is good enough. |
I will accept once you have a repository it works, I was testing by trying to create a fresh repository. It seems like it doesn't get enabled before we get the point where the clone gets performed? Can you provide an example of creating a fresh repository from a https source with authentication? ie:
|
I tried to write up the steps and I found exactly what you mean. So I pushed this fix 9a40fe2. Should work now. |
Would be nice to support the mercurial keyring extension so you don't have to specify passwords in plain text.
Biggest issue I have found so far is because interactive is 'off' it will not ask you for a password (just blows up with a repository error). It works once the password is stored in the keyring (ie if you checkout the repo in hg beforehand).
The text was updated successfully, but these errors were encountered: