From: Junio C Hamano <gitster@pobox.com>
To: "Harald Nordgren via GitGitGadget" <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org, "D. Ben Knoble" <ben.knoble@gmail.com>,
Harald Nordgren <haraldnordgren@gmail.com>
Subject: Re: [PATCH v4 2/2] remote: find tracking branches for URL push destinations
Date: Wed, 22 Jul 2026 12:03:00 -0700 [thread overview]
Message-ID: <xmqqpl0eoniz.fsf@gitster.g> (raw)
In-Reply-To: <08c432a2d4f52c202a2bebaa72330a17e94aedd1.1784743738.git.gitgitgadget@gmail.com> (Harald Nordgren via GitGitGadget's message of "Wed, 22 Jul 2026 18:08:58 +0000")
"Harald Nordgren via GitGitGadget" <gitgitgadget@gmail.com> writes:
> +static bool remote_has_push_url(struct remote *remote, const char *url)
> +{
> + const struct strvec *push_urls = push_url_of_remote(remote);
> +
> + for (size_t i = 0; i < push_urls->nr; i++) {
> + if (!strcmp(push_urls->v[i], url))
> + return true;
> + }
> + return false;
> +}
A new helper is very much welcome.
> void ref_push_report_free(struct ref_push_report *report)
> {
> while (report) {
> @@ -1887,13 +1898,45 @@ const char *branch_get_upstream(struct branch *branch, struct strbuf *err)
> return branch->merge[0]->dst;
> }
>
> -static char *tracking_for_push_dest(struct repository *repo UNUSED,
> +struct remote *repo_remote_for_push_tracking(struct repository *repo,
> + struct remote *remote)
> +{
> + const struct strvec *push_urls;
> + struct remote *first_match = NULL;
> + struct remote_state *remote_state = repo->remote_state;
> + const char *check_url;
> +
> + if (remote->origin != REMOTE_UNCONFIGURED)
> + return remote;
> +
> + push_urls = push_url_of_remote(remote);
> + if (push_urls->nr != 1)
> + return remote;
> + check_url = push_urls->v[0];
> +
> + for (int i = 0; i < remote_state->remotes_nr; i++) {
> + struct remote *candidate = remote_state->remotes[i];
> +
> + if (!candidate || candidate == remote ||
> + !remote_is_configured(candidate, 0) ||
> + !remote_has_push_url(candidate, check_url))
This part used to use remote_has_url(candidate, remote->url.v[0]),
which only looked at the .url and ignored .pushurl. Now it uses
remote_has_push_url() so we grab the effective push URL for the
remote we are dealing with and match it against the effective push
URL of the candidates. Looks correct.
> diff --git a/transport.c b/transport.c
> index fc144f0aed..30a4ab2cd5 100644
> --- a/transport.c
> +++ b/transport.c
> @@ -1553,8 +1553,11 @@ int transport_push(struct repository *r,
> if (!(flags & (TRANSPORT_PUSH_DRY_RUN |
> TRANSPORT_RECURSE_SUBMODULES_ONLY))) {
> struct ref *ref;
> + struct remote *tracking_remote = repo_remote_for_push_tracking(
> + r, transport->remote);
Personally, I would have line-wrapped the above more like this:
struct remote *tracking_remote =
repo_remote_for_push_tracking(r, transport->remote);
This is just for a future reference; it is certainly not critical
enough to warrant a new iteration just for this.
Thanks.
next prev parent reply other threads:[~2026-07-22 19:03 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-20 9:10 [PATCH 0/2] remote: resolve url push tracking Harald Nordgren via GitGitGadget
2026-07-20 9:10 ` [PATCH 1/2] remote: pass repository to push tracking helper Harald Nordgren via GitGitGadget
2026-07-20 18:23 ` Junio C Hamano
2026-07-20 9:10 ` [PATCH 2/2] remote: resolve URL-valued push tracking remotes Harald Nordgren via GitGitGadget
2026-07-20 18:49 ` Junio C Hamano
2026-07-20 19:56 ` Harald Nordgren
2026-07-20 23:49 ` Junio C Hamano
2026-07-21 16:11 ` Junio C Hamano
2026-07-21 8:58 ` [PATCH v2 0/2] remote: renamed remote push tracking Harald Nordgren via GitGitGadget
2026-07-21 8:58 ` [PATCH v2 1/2] remote: pass repository to push tracking helper Harald Nordgren via GitGitGadget
2026-07-21 8:58 ` [PATCH v2 2/2] remote: find tracking branches for URL push destinations Harald Nordgren via GitGitGadget
2026-07-21 14:28 ` [PATCH v2 0/2] remote: renamed remote push tracking D. Ben Knoble
2026-07-21 20:10 ` Harald Nordgren
2026-07-21 20:14 ` [PATCH v3 0/2] remote: url-based pushRemote with renamed remotes Harald Nordgren via GitGitGadget
2026-07-21 20:14 ` [PATCH v3 1/2] remote: pass repository to push tracking helper Harald Nordgren via GitGitGadget
2026-07-21 20:14 ` [PATCH v3 2/2] remote: find tracking branches for URL push destinations Harald Nordgren via GitGitGadget
2026-07-21 22:15 ` Junio C Hamano
2026-07-22 10:35 ` [PATCH v3 0/2] remote: url-based pushRemote with renamed remotes Ben Knoble
2026-07-22 18:08 ` [PATCH v4 " Harald Nordgren via GitGitGadget
2026-07-22 18:08 ` [PATCH v4 1/2] remote: pass repository to push tracking helper Harald Nordgren via GitGitGadget
2026-07-22 18:08 ` [PATCH v4 2/2] remote: find tracking branches for URL push destinations Harald Nordgren via GitGitGadget
2026-07-22 19:03 ` Junio C Hamano [this message]
2026-07-23 0:52 ` [PATCH v4 0/2] remote: url-based pushRemote with renamed remotes Junio C Hamano
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=xmqqpl0eoniz.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=ben.knoble@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=haraldnordgren@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