Unfriendly prompt for username/password about carthage HOT 5 CLOSED

Nice catch!

HTTPS cloning is uncool. Why not SSH? Or an option to choose

Generally, HTTPS is actually a better choice. Many users don't know how to (or don't want to) set up SSH keys. Both offer comparable transport security.

I agree that we should probably have an option to choose the default protocol. However, in addition to that, maybe we should try cloning over git:// first, and only fall back to HTTPS/SSH if the repository isn't publicly accessible.

It'd be nice to at least do one prompt at a time.

Yeahhh… this is a side effect of our Git clones being parallelized right now.

from carthage.

Aren't those all public repos? Why is it prompting for username/password at all?

from carthage.

@alanjrogers They're private @Carthage forks in this repo's Cartfile.

from carthage.

@jspahrsummers ah LOL.

from carthage.

So I think there are two actionable pieces of work here:

• Allow users to pull over SSH for GitHub repos. The default should remain HTTPS, IMO.
• Perform Git operations serially. This will fix other issues too, like interleaved logging.

from carthage.