-
Notifications
You must be signed in to change notification settings - Fork 30
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
Error cloning the repository #30
Comments
Hi Onur, thanks for the interest in our work. looks like we have another repo we need to make public. @diegoaldarondo can we make Animator public too? thanks |
Its already public but it might currently be pointing to ssh cloning
instead of https
…On Mon, Dec 14, 2020, 9:35 AM Timothy Dunn ***@***.***> wrote:
Hi Onur, thanks for the interest in our work. looks like we have another
repo we need to make public.
@diegoaldarondo <https://github.com/diegoaldarondo> can we make Animator
public too? thanks
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#30 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACYHDXDXO7FYULRJNW6EJ4LSUYPBZANCNFSM4U22EFPQ>
.
|
Hi! Great, I was worried that the package might not be ready for end-users yet! @diegoaldarondo Is there anything I could do to resolve this? |
Hi Onur, Its probably just a ssh vs https cloning error. I'll change the repository to use https by default. Best, |
@diegoaldarondo Thanks a lot for the assistance, looking forward to give it a try and see if I manage to get it running! Best, |
Ok, everything should now be using https by default. Let me know if it works for you, and thanks for bringing this up! |
Thanks a lot for the assistance, cloning is working now! |
Hello!
Promising tool for behavioral experiments, looks much better than DLC!
However I guess some parts of the repository is still private as I am getting the following error when I try to clone the repository:
Could you perhaps provide some assistance with the issue?
Best regards,
Onur
The text was updated successfully, but these errors were encountered: