https://github.com/JuliaLang/julia/issues/16041
We can continue this discussion there. I think that issue should get a 0.5.0 label, i.e. this should be treated as a regression that has to be fixed before 0.5 can be released. Cheers, David From: [email protected] [mailto:[email protected]] On Behalf Of David Anthoff Sent: Monday, April 25, 2016 11:16 AM To: [email protected] Subject: RE: [julia-users] Cloning private package with 0.5 That doesn’t work for bitbucket repos, though… From: [email protected] <mailto:[email protected]> [mailto:[email protected]] On Behalf Of Jacob Quinn Sent: Sunday, April 24, 2016 8:49 PM To: [email protected] <mailto:[email protected]> Subject: Re: [julia-users] Cloning private package with 0.5 Note that it's currently possible to clone private GitHub repos using "personal access tokens" from Github. If you go to your profile/settings, you can generate private access tokens that allow access to private Github repos and then from Julia, you can clone with the following format: Pkg.clone("https://username:[email protected]/username/private_repo.jl";) On Fri, Apr 22, 2016 at 5:57 PM, Eric Forgy <[email protected] <mailto:[email protected]> > wrote: I have the same problem (on Windows) and really hoping this gets fixed before 0.5 is released. I have a ton of private repos. I'd prefer a solution that lets me keep my remotes at [email protected]:EricForgy/MyPrivateRepo.jl <mailto:[email protected]:EricForgy/MyPrivateRepo.jl> . It would be more than a little annoying if I have to change every one to https. Hopefully, Pkg can do some magic and make the changes for me if needed.
