-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
Projects seem to break when git modules paths change #5928
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
Comments
please see this : #5884 |
The error is because your We only support http urls at the moment (looks like we should improve the msg error) |
Thanks for the feedback, changing the submodule URL to https fixed it. I see two issues then:
|
Thanks for the suggestions. The main restriction is because we don't support private repositories in our community site. There are some ideas in how to support public repositories with I'm opening a new issue to improve the error message |
Details
Expected Result
When the path of a git module changes I'd expect the background logic to do the proper sync operations (change
.gitmodules
, prune the previous module,git submodule sync
,git submodule update
) and seamlessly migrate to the new path.Actual Result
RTD seems to try to clone the submodule into the existing folder without cleaning it up first, ending up with an error like:
The text was updated successfully, but these errors were encountered: