-
Notifications
You must be signed in to change notification settings - Fork 223
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
No support for submodules #290
Comments
and thanks for this plugin! ^__^ |
I'm working with submodule on a daily basis and it works for me. I assume that if you manually navigate to the submodule's directory and invoke Please at least state your OS and git version. |
You assume right - git diff shows no differences. |
Is it reproducible for you on any public repo, so that I could try it locally? It works with the submodule for me in my repo. |
Created brand new projects, both on GitHub and BitBucket, but could not reproduce - worked as expected. So it's some problem with my repo. |
This issue may be caused by some versions of git itself. Some git commands randomly fail, if git is not called from within the working tree, but this is exactly what GitGutter does. I prepared a fix to run all git commands from within the working tree, which is published as soon as all required PRs are accepted. |
Should work with GitGutter 1.5.0. Same as with work-tree support. Please check. |
It works with 1.5.0! (^O^)/ |
I have a git submodule within my git project. When I open a submodule file in Sublime I see plus signs beside all the lines, as if the entire content is newly added.
The text was updated successfully, but these errors were encountered: