2.38.1 introduces a change (due to CVE-2022-39253) that disables git submodule add using the file protocol.
➜ product git:(master) git submodule add ../remote
Cloning into '/Users/.../git-katas/submodules/exercise/product/remote'...
fatal: transport 'file' not allowed
fatal: clone of '/Users/.../git-katas/submodules/exercise/remote' into submodule path '/Users/.../git-katas/submodules/exercise/product/remote' failed
Apparently this can be alleviated by setting git config --global protocol.file.allow always.
Unfortunately this can not be solved with a --local setting as that only applies to the parent repo, not the submodule.
I would prefer not to have the setup.sh script mess with users global config, especially regarding something security related, but we need a solution.
Using git -c protocol.file.allow=always submodule add ../remote works, but is not a nice command to have to explain in a kata.
2.38.1 introduces a change (due to CVE-2022-39253) that disables
git submodule addusing the file protocol.Apparently this can be alleviated by setting
git config --global protocol.file.allow always.Unfortunately this can not be solved with a
--localsetting as that only applies to the parent repo, not the submodule.I would prefer not to have the setup.sh script mess with users global config, especially regarding something security related, but we need a solution.
Using
git -c protocol.file.allow=always submodule add ../remoteworks, but is not a nice command to have to explain in a kata.