Gábor Csárdi

I don't mind if it lives here. So the same questions apply to devtools then. Thanks!

I think `is_cran` here simply means "it is coming from a CRAN-like repository", and it does not actually mean that it is a package on CRAN.

Using the full SHA works, though: ```r remotes::install_git( "[email protected]:tidyverse/stringr.git@dd909b714b20ff3add2eedb0a1c917ba6938e40e", git = "external" ) ``` Isn't this good enough?

I like the idea of warning for short SHAs for (x)git remotes. It would be great to make the short SHAs work, but deep cloning can also be really bad...

Can you use install_git() instead? That should work with ssh keys I believe. install_github() uses the GitHub API, and I am not sure if the API works with ssh keys.

True, but this is a breaking change, right? Or can you implement sg. that helps the transition? E.g. automatically moving it over to private, with a warning?

Experiments with winpty are quite promising so far.

This is quite difficult to implement on Windows, unfortunately. The closest I got is this, maybe this is doable with some more effort: 1. Create a pipe server in the...

Yeah, I guess this is more of a processx feature, I'll move it over there.

Can you please include the error message from keyring?