Git development
 help / color / mirror / Atom feed
From: "Éric NICOLAS" <ccjmne@gmail.com>
To: git@vger.kernel.org
Cc: gitster@pobox.com, jacob.keller@gmail.com,
	"Éric NICOLAS" <ccjmne@gmail.com>
Subject: [PATCH v2] submodule: resolve insteadOf aliases when matching remote
Date: Thu, 23 Jul 2026 02:21:32 +0200	[thread overview]
Message-ID: <20260723002132.3989727-1-ccjmne@gmail.com> (raw)
In-Reply-To: <20260721213042.3357346-1-ccjmne@gmail.com>

When ca62f524c1 (submodule: look up remotes by URL first, 2025-06-23)
introduced a mechanism to identify which remote is to be used by a
submodule, it compared the URL stored in the .gitmodules inventory to
that of each available remote.

The URLs of remotes are rewritten according to url.<base>.insteadOf,
whereas those stored in the .gitmodules aren't.  When such aliasing
applies, no match can be made between the two corresponding sides, and
the procedure degrades to its fallback logic electing either the only
configured remote if there is only one, or "origin" otherwise.

That behaviour is unfortunate when no remote is called "origin",
because its last resort will have a submodule update command look for a
non-existent remote-tracking reference and fail to proceed, instead of
using the remote whose rewritten URL matches.

Resolve the alias in the URL inventoried in .gitmodules before comparing
it against those of the corresponding submodule's configured remotes.

Signed-off-by: Éric NICOLAS <ccjmne@gmail.com>
---
Thank you for your guidance.

Changes in v2:

- Reword the commit message more purposefully
- Adjust the implementation as suggested, avoiding a superfluous
  variable
- Tidy up the integration test

 remote.c                    | 14 +++++++++++---
 t/t7406-submodule-update.sh | 19 +++++++++++++++++++
 2 files changed, 30 insertions(+), 3 deletions(-)

diff --git a/remote.c b/remote.c
index b17648d6ef..b1fed58e79 100644
--- a/remote.c
+++ b/remote.c
@@ -1821,17 +1821,25 @@ const char *repo_default_remote(struct repository *repo)
 
 const char *repo_remote_from_url(struct repository *repo, const char *url)
 {
+	char *rewritten_url;
+	const char *remote_name = NULL;
+
 	read_config(repo, 0);
+	if ((rewritten_url = alias_url(url, &repo->remote_state->rewrites)))
+		url = rewritten_url;
 
 	for (int i = 0; i < repo->remote_state->remotes_nr; i++) {
 		struct remote *remote = repo->remote_state->remotes[i];
 		if (!remote)
 			continue;
 
-		if (remote_has_url(remote, url))
-			return remote->name;
+		if (remote_has_url(remote, url)) {
+			remote_name = remote->name;
+			break;
+		}
 	}
-	return NULL;
+	free(rewritten_url);
+	return remote_name;
 }
 
 int branch_has_merge_config(struct branch *branch)
diff --git a/t/t7406-submodule-update.sh b/t/t7406-submodule-update.sh
index 9554720152..10adeabf0f 100755
--- a/t/t7406-submodule-update.sh
+++ b/t/t7406-submodule-update.sh
@@ -256,6 +256,25 @@ test_expect_success 'submodule update --remote should fetch upstream changes' '
 	)
 '
 
+test_expect_success 'submodule update --remote resolves URL rewrites' '
+	test_config_global "url.$(pwd)/.insteadOf" local: &&
+	mkdir alias-super alias-submodule &&
+	(
+		cd alias-submodule &&
+		git init &&
+		git commit --allow-empty --message "Initial commit"
+	) &&
+	(
+		cd alias-super &&
+		git init &&
+		git submodule add local:alias-submodule submodule &&
+		git submodule update --force &&
+		git -C submodule remote rename origin upstream &&
+		git -C submodule remote add fork user@host &&
+		git submodule update --remote
+	)
+'
+
 test_expect_success 'submodule update --remote should fetch upstream changes with .' '
 	(
 		cd super &&

Range-diff against v1:
1:  ed507998b3 ! 1:  4363eb3cb1 submodule: resolve insteadof-aliases when matching remote
    @@ Metadata
     Author: Éric NICOLAS <ccjmne@gmail.com>
     
      ## Commit message ##
    -    submodule: resolve insteadof-aliases when matching remote
    +    submodule: resolve insteadOf aliases when matching remote
     
    -    When ca62f524c1 introduced a mechanism to identify which remote is to be
    -    used by a submodule, we had it compare the URL stored in the .gitmodules
    -    inventory to those of each available remote.
    +    When ca62f524c1 (submodule: look up remotes by URL first, 2025-06-23)
    +    introduced a mechanism to identify which remote is to be used by a
    +    submodule, it compared the URL stored in the .gitmodules inventory to
    +    that of each available remote.
     
    -    However, when using URL aliasing via url.<base>.insteadOf, we store
    -    in .gitmodules the URL pre-resolution of the alias, whereas the
    -    corresponding remote set up in the submodule reports using the
    -    *resolved* URL.  This mechanism therefore fails to find a match then,
    -    and resorts to the fallback logic, which does use either the only
    -    configured remote if there is only one, or attempts using "origin"
    -    otherwise.
    +    The URLs of remotes are rewritten according to url.<base>.insteadOf,
    +    whereas those stored in the .gitmodules aren't.  When such aliasing
    +    applies, no match can be made between the two corresponding sides, and
    +    the procedure degrades to its fallback logic electing either the only
    +    configured remote if there is only one, or "origin" otherwise.
    +
    +    That behaviour is unfortunate when no remote is called "origin",
    +    because its last resort will have a submodule update command look for a
    +    non-existent remote-tracking reference and fail to proceed, instead of
    +    using the remote whose rewritten URL matches.
     
         Resolve the alias in the URL inventoried in .gitmodules before comparing
         it against those of the corresponding submodule's configured remotes.
    @@ remote.c: const char *repo_default_remote(struct repository *repo)
      const char *repo_remote_from_url(struct repository *repo, const char *url)
      {
     +	char *rewritten_url;
    -+	const char *url_to_match;
     +	const char *remote_name = NULL;
     +
      	read_config(repo, 0);
    -+	rewritten_url = alias_url(url, &repo->remote_state->rewrites);
    -+	url_to_match = rewritten_url ? rewritten_url : url;
    ++	if ((rewritten_url = alias_url(url, &repo->remote_state->rewrites)))
    ++		url = rewritten_url;
      
      	for (int i = 0; i < repo->remote_state->remotes_nr; i++) {
      		struct remote *remote = repo->remote_state->remotes[i];
    @@ remote.c: const char *repo_default_remote(struct repository *repo)
      
     -		if (remote_has_url(remote, url))
     -			return remote->name;
    -+		if (remote_has_url(remote, url_to_match)) {
    ++		if (remote_has_url(remote, url)) {
     +			remote_name = remote->name;
     +			break;
     +		}
    @@ t/t7406-submodule-update.sh: test_expect_success 'submodule update --remote shou
      
     +test_expect_success 'submodule update --remote resolves URL rewrites' '
     +	test_config_global "url.$(pwd)/.insteadOf" local: &&
    -+	mkdir aliased-super aliased-submodule &&
    ++	mkdir alias-super alias-submodule &&
     +	(
    -+		cd aliased-submodule &&
    ++		cd alias-submodule &&
     +		git init &&
    -+		echo line >file &&
    -+		git add file &&
    -+		git commit -m "Initial commit"
    ++		git commit --allow-empty --message "Initial commit"
     +	) &&
     +	(
    -+		cd aliased-super &&
    ++		cd alias-super &&
     +		git init &&
    -+		git submodule add local:aliased-submodule submodule &&
    -+		git submodule update --force submodule &&
    ++		git submodule add local:alias-submodule submodule &&
    ++		git submodule update --force &&
     +		git -C submodule remote rename origin upstream &&
     +		git -C submodule remote add fork user@host &&
    -+		git submodule update --remote submodule
    ++		git submodule update --remote
     +	)
     +'
     +
-- 
2.55.0


      parent reply	other threads:[~2026-07-23  0:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-21 21:30 [PATCH] submodule: resolve insteadof-aliases when matching remote Éric NICOLAS
2026-07-22 19:49 ` Junio C Hamano
2026-07-23  0:21 ` Éric NICOLAS [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20260723002132.3989727-1-ccjmne@gmail.com \
    --to=ccjmne@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=jacob.keller@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox