-
Notifications
You must be signed in to change notification settings - Fork 147
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
.git of Submodule not followed #67
Comments
Maybe it's time to vendor Grit... |
The grit devs recommend https://github.com/libgit2/rugged |
Oh, interesting! If someone wants to take a crack at converting git-up to use rugged, that'd be incredible - I'm afraid I'm far too busy right now ;_; |
+1 for this issue. Looks like Grit is no longer maintained so a migration to libgit2/rugged is eventually necessary. |
Just ran into this again. Maybe I'll give it a go. |
+1 |
👍 it would be awesome |
+1 |
+1 👍 |
I've switched to https://github.com/msiemens/PyGitUp |
So, I have a repo with some submodules. I wanted to use git-up in one of the submodules, but rather than a .git folder, it had a .git FILE containing a relative path to the actual .git folder (like "../../.git/modules/SomeFolder/SubmoduleName"). Git itself seems to be ok with it, but git-up complains "Not a directory". Now, if I renamed the .git file and instead made a symbolic link to the relevant git folder, git-up worked fine. It SEEMS like maybe this shouldn't be too hard to fix, just to follow the link in the .git file if it isn't a directory.
The text was updated successfully, but these errors were encountered: