From: Jacob Keller <jacob.keller@gmail.com>
Date: Tue, 04 Oct 2022 17:43:10 GMT
Subject: issue with submodules using origin remote unexpectadly
Message-ID: <CA+P7+xrnAXceHJbBYV8Z9Ay9xbkzpiX3P0wXLwN7jfnifW2OBQ@mail.gmail.com>

Hi,

I've been running into an issue with submodules trying to fetch using
"origin" even though the submodule does not have a remote by that
name. (I recently switched the submodule remote name)

remote: Enumerating objects: 210, done.
remote: Counting objects: 100% (207/207), done.
remote: Compressing objects: 100% (54/54), done.
remote: Total 210 (delta 123), reused 197 (delta 119), pack-reused 3
Receiving objects: 100% (210/210), 107.20 KiB | 4.29 MiB/s, done.
Resolving deltas: 100% (123/123), completed with 48 local objects.
From <redacted>
...
Fetching submodule submodule
From <redacted>
   85e0da7533d9..80cc886f1187  <redacted>
Fetching submodule submodule2
fatal: 'origin' does not appear to be a git repository
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.
Errors during submodule fetch:
        submodule2


I thought at first there might be some configuration value in the
parent that is selecting origin, but I can 't find one. I also thought
maybe its some sort of defaulting to origin but I looked through
submodule code and didn't find one.

Is it just that submodule code is not resilient against changing the
default remote name away from origin?

Thanks,
Jake