4 ms·
That's because you haven't had all code messed up when someone pushed in the wrong order :-)
by Dm_Linov 4y ago
That's because you haven't had all code messed up when someone pushed in the wrong order :-)
- Denvercoder9 4y agoHow can pushing in the wrong order mess up all code? The worst thing I can imagine is pushing the superproject with a subproject update, but not pushing the subproject. That would end up with an unbuildable commit in the superproject, as you can never check out its associated commit from the subproject, but I don't see how that's close to "messing up all code".
- Dm_Linov 4y agohttps://codingkilledthecat.wordpress.com/2012/04/28/why-your-company-shouldnt-use-git-submodules/ https://codingkilledthecat.wordpress.com/2012/04/28/why-your... - there's a good example here
- _jplc 4y agoNotice the post is 10 years old and some of the complaints can get solved with the config `submodule.recurse true` https://stackoverflow.com/a/49427199 https://stackoverflow.com/a/49427199