-
Notifications
You must be signed in to change notification settings - Fork 2
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
Git clone urls #7
Comments
I'll check and revert on the 24th of Jan |
Hi Domizio (@ddnexus) Apologies for the delay: There are two protocols which can be used to clone: SSH and https. Can you confirm the the following does not work:
If ssh does not work, then perhaps this might be the solution? If you could confirm on your end that would be appreciated. |
I always use https because I use different and new created docker containers to clone and try other repos, so I never need ssh for virtual tries. Admittedly my question was not clear: let me rephrase it. Do you really want to impose the use of ssh to a user just to clone a public demo? Shouldn't that be as accessible as possible? That is a nuisance in my case because I had to manually do it with https. However if you think that someone would find ssh more desirable, maybe you could write both. |
Both should work. Thx for clarifying. Will get to the bottom of this. |
I tried this one three different computers, linux, windows x2 and could not reproduce the issue: all them seemed to work fine with https. perhaps i'm misunderstanding the issue? any ideas? |
Indeed the issue is ssh, not https. 🙂 |
I've switched to https in the readme. That should solve 99% of the problems, i think. |
Shouldn't the URL be simply
https://github.com/benkoshy/pagy-rails.git
?The text was updated successfully, but these errors were encountered: