3 ms·
I'm dying laughing > submodules? they're a file in the repo with a special type inside the trees, git knows when checking out that the file is special, and cou
by x0x0 3y ago
I'm dying laughing
> submodules? they're a file in the repo with a special type inside the trees, git knows when checking out that the file is special, and could run other commands. it then does not run those commands and the person using submodules begins crying.
For a while, at my company, we used a git submodule (err, I unfortunately used a git submodule... this was my fault) and it was tradition for every new engineer to have a bad deploy because git silently ignores the submodule not existing on disk. So they would deploy, the submodule would be missing, and boom.
- Buttons840 3y agoYour deploy process says nothing if several (possibly thousands? a submodule can be big) files are missing and this is a complaint you have about git? It sounds like more of a complaint about the deploy process.
- x0x0 3y agoThere certainly were defects in the deploy process, and we have since moved to a much better method. This was our docs tree, so it didn't break the code, just the, well, public documentation. It just was annoying that you can use a submodule but git will happily ignore it not existing. It just made the whole thing super janky.
- rwmj 3y agoJust wait until you bisect in a tree that contains a submodule, forget the mandatory manual update step, and your day long bisection is wasted. If you have to bisect across commits that added or removed a submodule you might as well give up now.