GitHub Community
Clone --recurse-submodules permission denied #21659
-
|
Hope this is the right section.
|
Beta Was this translation helpful? Give feedback.
Replies: 4 comments
-
|
👋 Welcome! First - feel free to use codeblocks - that should allow a lot more freedom with sharing output. Just enclose the output in backticks or use the It looks as though the remote url for the submodule is using SSH and not HTTPS, which you are using to clone the main repository. This means that you’d need an SSH key for this to complete. It’s not finding a valid key, so this fails. The path of least resistance here is probably creating an SSH key and cloning with SSH. The submodule url can be changed as well, but obviously that’s easier done after you’ve cloned the project. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the reply. |
Beta Was this translation helpful? Give feedback.
-
|
The repository itself is fine either way - you can clone using HTTPS or SSH, that doesn’t matter. But the way this particular submodule was set up, You can read more about |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for that link. |
Beta Was this translation helpful? Give feedback.
👋 Welcome!
First - feel free to use codeblocks - that should allow a lot more freedom with sharing output. Just enclose the output in backticks or use the
</>option in the formatting bar. Links formatted that way shouldn’t cause any hassle.It looks as though the remote url for the submodule is using SSH and not HTTPS, which you are using to clone the main repository. This means that you’d need an SSH key for this to complete. It’s not finding a valid key, so this fails.
The path of least resistance here is probably creating an SSH key and cloning with SSH.
The submodule url can be changed as well, but obviously that’s easier done after you’ve cloned the project.