You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So, a colleague has a repository with a submodule that's been removed incorrectly. The link still persists in the tree somehow, but the .gitmodules file has been removed.
The checkout step is defined to not checkout the submodules, but it still fails in setting up the auth:
Run actions/checkout@v2
with:
ref: <ref>
fetch-depth: 0
repository: <repo>
token: ***
ssh-strict: true
persist-credentials: true
clean: true
lfs: false
submodules: false
set-safe-directory: true
/usr/bin/git config --local --name-only --get-regexp core\.sshCommand
/usr/bin/git submodule foreach --recursive git config --local --name-only --get-regexp 'core\.sshCommand' && git config --local --unset-all 'core.sshCommand' || :
Error: fatal: No url found for submodule path 'src/submodule' in .gitmodules
Error: The process '/usr/bin/git' failed with exit code 128
Why is the submodule command even being run? Does it have to?
The text was updated successfully, but these errors were encountered:
It does appear to be related, but I don't know if they're trying to explicitly disable submodules or not. It seems to me that if 'false', it shouldn't try setting up the submodules on first clone. 🤷
So, a colleague has a repository with a submodule that's been removed incorrectly. The link still persists in the tree somehow, but the .gitmodules file has been removed.
The checkout step is defined to not checkout the submodules, but it still fails in setting up the auth:
Why is the submodule command even being run? Does it have to?
The text was updated successfully, but these errors were encountered: