Hi all, I am a maintainer for github.com/idaholab/moose. I had a developer submit a pull request the other day trying to update our libmesh submodule, which as specified through our `.gitmodules` points to github.com/libmesh/libmesh. The wrinkle is that the submodule hash he wanted to update to actually corresponded to an un-merged pull request commit, e.g. a commit that didn't fall under any of the upstream branch's histories. Yet oddly many of our test-boxes were still able to checkout his submodule hash. This behavior wouldn't surprise me if our test boxes were configured to fetch pull request refs as well as branch and tag refs, e.g.
git config --global --add remote.origin.fetch "+refs/pull/*/head:refs/remotes/origin/pr/*" but they're not. Does anyone have a theory for why `git submodule update --init` was able to fetch this un-merged PR commit for many of our test-boxes but why for some we got the error that I expected to receive in all cases? BUILD_ROOT/moose/: git submodule update --init Submodule 'libmesh' (g...@github.com:libMesh/libmesh) registered for path 'libmesh' Cloning into 'libmesh'... fatal: reference is not a tree: a258ca240d76e406810095fec6129e27950753f2 Unable to checkout 'a258ca240d76e406810095fec6129e27950753f2' in submodule path 'libmesh' -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/git-users/11a9d3e4-e57d-439c-a5f3-e7062823f0a8%40googlegroups.com.
