Re: [PATCH v10 1/5] fetch: add remote.<name>.refmap
- From
Harald Nordgren <haraldnordgren@gmail.com>
- Date
- Oct 30, 2026, 10:14 UTC
- Message-ID
- <CAHwyqnUzKAD42qTMbAV_9DttzP91PUTjHxXehy1cX0=B7e0cbg@mail.gmail.com>
- In-Reply-To
- <xmqqmrrwywq8.fsf@gitster.g>
On Fri, Oct 30, 2026 at 12:21 AM Junio C Hamano <gitster@pobox.com> wrote:
Show 14 quoted lines
> > Ben Knoble <ben.knoble@gmail.com> writes: > > > Yes, I would love to add pushRefmap atop later! It would > > ease my working with notes, I think. > > > Yes, I would love to add pushRefmap atop later! It would > > ease my working with notes, I think. > > Tell us more when you are off mobile ;-). > > I do not think I planned to add '--refmap' support on the push side, > even from the command line, but I can imagine there would be > reasonable workflows that benefit from having one.
Not sure if it's related to this specific conversation, but I realized that @{push} is not being resolved here, so I plan on adding a small fix in a v13:
```
--- a/remote.c +++ b/remote.c @@ -2018,6 +2018,8 @@ static char *tracking_for_push_dest(struct repository *repo, remote = repo_remote_for_push_tracking(repo, remote); ret = apply_refspecs(&remote->fetch, refname); + if (!ret) + ret = apply_refspecs(&remote->refmap, refname); if (!ret) return error_buf(err, _("push destination '%s' on remote '%s' has no local tracking branch"), ``` Harald