-
Notifications
You must be signed in to change notification settings - Fork 291
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fails to clone private submodules #87
Comments
Hi there! We use Pivotal Tracker to provide visibility into what our team is working on. A story for this issue has been automatically created. The current status is as follows:
This comment, as well as the labels on the issue, will be automatically updated as the status in Tracker changes. |
Does the sub-repo permit that key? One gotcha is with deploy keys, they can only be bound to one repo. You may need to create a CI user that configures the key instead. I'm not sure if there's anything else we can do here; we tried permitting configuration of multiple keys before, but it turned out that |
Yep. I am not using a deploy key, I am using a user key, and the user owns both repos. As I said,
|
Sorry for the delay on this; by now you may have moved on, but just to sanity check, this could easily be a syntax thing. Make sure the key looks like: foo: |
blah blah blah and not something like: foo: |-
blah blah blah (note the hyphen) Beyond something like that or a paste error (pasting private keys with vim can go poorly for example) I'm not sure what else would be the issue. We just add the key to the keychain as normal and git clone as normal, so I don't see why it wouldn't work. |
This issue has been open for a while and become stale. I'm going to close it now. |
Actions has the same problem, see the discussion actions/checkout#183 |
It seems that it does not use ssh key to do submodule init. I can clone my repo and its submodules separately (using the same ssh key) and each succeeds, but unless I say
{ submodules: none }
when doing theget
on the parent, the parent fails to clone with:The text was updated successfully, but these errors were encountered: