-
Notifications
You must be signed in to change notification settings - Fork 3
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
Unable to update #8
Comments
Yeah, this is an unknown issue with https. It's because we are running the
fetch in parallel.
If you have setup ssh key on github, you can try command to switch the
protocol to ssh. `hr cmd use_git_ssh`.
…On Wed, Oct 18, 2017 at 10:25 AM, Henrikas Elsbergas < ***@***.***> wrote:
I think we need to update repository origins to use ssh instead of ssh.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#8 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAhJ90C7LwBDLK-bA7gIuy-suhOdCQ-Eks5stWF9gaJpZM4P9Bo9>
.
|
The issue still remains. Would it be possible to get rid of using https and developer keys completely? It seems to be a security vulnerability at the moment. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Not sure why github token isn't working. Unable to enter credentials manually - password is interpreted as a username
The text was updated successfully, but these errors were encountered: