On Tue, 6 Aug 2019 17:54:20 +0200 Mateusz Loskot <mate...@loskot.net> wrote:
> On Tue, 6 Aug 2019 at 16:04, Jason Sewall <jasonsew...@gmail.com> wrote: > > > > Submodules are great, and I used them at work. The problem is, people > > wind up cloning my repos without --recursive and then nothing works > > for them, because the submodules weren't populated and those > > ultimately are needed to build my code. > > What you need is a simple document for your team that outlines the common > Git workflow or README.md in root directory of your repositories with > fat heading: > > ## Clone > > ``` > git clone --recursive ... > ``` > > > A team in another company may require non-recursive clones by default > and warnings from git may be quite annoying. Given the fact there is not > one but may valid "my way"-s available, acceptable and supported by Git, > I think, babysitting behaviour is not quite aligned with its philosophy, is > it? It has warnings that you can disable globally or per-repository in configuration to fit your workflow. Thanks Michal
