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
This issue has been brought up a few times (ocurrent/ocluster#179, ocurrent/ocaml-ci#323) but I thought I would open it on the repository where the fix/feature would have to start!
Currently, current_git does not support checking out private repositories. For now, I'll limit the discussion to Github repos. There's a few ways off of the top of my head you could go about trying to fix this:
Passing in a Github token to be placed in the URL when doing the fetch. Something like this code with some overriding of the pp_cmd to not leak the token in the logs. This works until your submodules are also private.
Setup either the main account on the machine you are running to have access to Github or setup some user on the machine with access and run git as them. This doesn't feel great and probably will have permission errors.
There might be some sort of thing we can with git-credentials and a token to overcome the submodule problem, I'm not sure.
Any other ideas?
The text was updated successfully, but these errors were encountered:
This issue has been brought up a few times (ocurrent/ocluster#179, ocurrent/ocaml-ci#323) but I thought I would open it on the repository where the fix/feature would have to start!
Currently,
current_git
does not support checking out private repositories. For now, I'll limit the discussion to Github repos. There's a few ways off of the top of my head you could go about trying to fix this:token
to be placed in the URL when doing the fetch. Something like this code with some overriding of thepp_cmd
to not leak the token in the logs. This works until your submodules are also private.git
as them. This doesn't feel great and probably will have permission errors.git-credentials
and a token to overcome the submodule problem, I'm not sure.Any other ideas?
The text was updated successfully, but these errors were encountered: