You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 17, 2021. It is now read-only.
I was reading through the source code, wondering how you handle private repositories and stuff. I am not sure it's a good idea to implement private repositories by just prepending git@ or so. That will not work if the hosting service is not GitHub or BitBucket, there can be some other username people might want to use. Or they might feel like cloning over https.
To put it simply, it could make sense to do something similar to what package.json for NPM does:
Hi,
I was reading through the source code, wondering how you handle private repositories and stuff. I am not sure it's a good idea to implement private repositories by just prepending
git@
or so. That will not work if the hosting service is not GitHub or BitBucket, there can be some other username people might want to use. Or they might feel like cloning over https.To put it simply, it could make sense to do something similar to what
package.json
for NPM does:And something similar for other versioning systems.
What do you think?
Regards,
Ondrej Kupka
The text was updated successfully, but these errors were encountered: