Re: Suggestion: git clone should warn if repository has submodules

From: Mateusz Loskot <mateusz@loskot.net>
Date: Aug 6, 2019, 15:54 UTC
Message-ID: <CABUeae9JhQ+JcNzYRMr40T2FTCJChYEz_riUr6Q1O5YO0uEDng@mail.gmail.com>
In-Reply-To: <CADqa0D5wVWk2wa-raeVmCEhCqYznpba4TeUW_7UQOA0huR-RAg@mail.gmail.com>

On Tue, 6 Aug 2019 at 16:04, Jason Sewall <jasonsewall@gmail.com> wrote:

Show 5 quoted lines

>
> 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?

Best regards,

-- 
Mateusz Loskot, http://mateusz.loskot.net