Failed shallow submodule clone for fixed SHA1 falls back to checking out HEAD
- Date: Tue, 18 Apr 2017 15:04:17 +0200
- From: Sebastian Schuberth <sschuberth@xxxxxxxxx>
- Subject: Failed shallow submodule clone for fixed SHA1 falls back to checking out HEAD
this is using "git version 2.12.2.windows.2" on Windows / "git version 2.12.2-639-g584f897" on Linux.
I have configured my superproject with .gitmodules saying
path = src/funTest/resources/projects/external/jgnash
url = https://github.com/ccavanaugh/jgnash.git
shallow = true
and configured the submodule to checkout commit 2aa4cce7d7fd46164030f2b4d244c4b89e77f722 . When doing a fresh clone of my superproject via "git clone --recursive" I get
error: Server does not allow request for unadvertised object 2aa4cce7d7fd46164030f2b4d244c4b89e77f722
Fetched in submodule path 'src/funTest/resources/projects/external/jgnash', but it did not contain 2aa4cce7d7fd464030f2b4d244c4b89e77f722. Direct fetching of that commit failed.
So far so good, it simply seems that GitHub does not support allowReachableSHA1InWant . The interesting bit is that my submodule checkout still ends up being shallow, but poiting to HEAD:
$ cd src/funTest/resources/projects/external/jgnash
$ git log
commit 12036fffb6c620515edd96416363fd1749b5d003 (grafted, HEAD -> master, origin/master, origin/HEAD)
Author: Craig Cavanaugh <jgnash.devel@xxxxxxxxx>
Date: Tue Apr 18 05:33:06 2017 -0400
Wouldn't it make more sense to unshallow the submodule clone in this case and checkout the configured commit 2aa4cce7d7fd46164030f2b4d244c4b89e77f722 afterwards? At least I'd be getting what I asked for in that case, even if at the cost of additional network traffic. Because if I read  correctly, the command line option belonging to "submodule.<name>.shallow" is called "--[no-]recommend-shallow", i.e. it's only a recommendation, to falling back to a full clone should be fine.