GitSavvy
GitSavvy copied to clipboard
`git: submodule`
Special view with:
- [ ] list of all submodules with commit status
- [ ] summary for each submodule
- [ ] initialize new submodule
- [ ] update
Are people still using submodule. Nearly everybody I know switched to git subtrees?
We still use it for some projects internally - but I'm deferring this (that's basically what my next-next milestone is for) until I can dig in and see if it is worth the effort. I can take a look at subtrees too.
A lot of people on Windows use submodules instead of subtrees since subtrees is not easily installed, while submodules ships with Git itself.
As far as this feature (view/interface) goes, not sure if it's necessary, it's not something you change a lot.
subtrees are part of git since version 1.7.11. But they do not need an interace in GitSavvy, because once initialised they blend in with the normal tree.
@TheHippo 
@p3lim Interesting. I'm exclusively develop on Linux and git subtree installed everywhere since mid 2012.
@TheHippo Which is why I specifically said Windows in https://github.com/divmain/GitSavvy/issues/31#issuecomment-82935088 :smile:
I wouldn't say subtree replaces submodule, both have their use cases and differ in how git commands (such as commit/push/pull) effect them. And I really would appreciate submodule support right now :)
In particular, some commands work on submodules automatically (status/commit), but others (graph/log) only work on the parent. @divmain do you want separate issue/s for this?
If there's enough interest in subtree, it should be in a separate issue.
We use a lot submodules in tens of projects because they fit our needs perfectly. submodules get improved as Git evolves: you can see them mentioned in the release notes here and there. I think it's a living feature, not something going to die. I would really appreciate to be able to manage them with this great plugin.
Agreed @redihokuto. Submodules will happen sometime, but they're a low priority for the team. Sometimes I get free evenings and burn through a few issues - I'll keep this one in mind for the next time that happens!
maybe it's time?