Change from this:
curl https://bitbucket.org/site/ssh >> ~/.ssh/known_hosts
To this: (curl https://bitbucket.org/site/ssh; echo) >> ~/.ssh/known_hostsYou may have missed the part about "telling people they can trust the vendor instructions"...
Umm, why don’t you just use git over HTTPS?
Much worse performance (which might have been idiosyncratic, or might have been improved in recent years, but repeated authentication vs. single stream design hasn't changed.)
Thanks for pointing this out, I'll put in a PR to fix that up today.
cool, thanks! I'm sort of surprised it didn't get attention via some other path, but then I never got around to filling a ticket myself :-)
Optimistically, I like to think that people were just not _quite_ bothered enough to file a bug report. The pessimist in me thinks that people went back to blindly typing "yes" when prompted. Either way, thanks for the feedback, the fix should be live!
Didn't work, because there's no trailing newline on the output of site/ssh. So even if it works, it corrupts the next addition.