Re: [PATCH 0/3] Add support for per-remote and per-namespace SSH options

From: Wesley <wesleys@opperschaap.net>
Date: Mar 27, 2026, 15:04 UTC
Message-ID: <abe2616d-4dbc-4d84-9fa9-a6d24cd65927@opperschaap.net>
In-Reply-To: <7d3731c5-d766-47f5-af60-813b379cbeef@kdbg.org>

On 3/27/26 03:51, Johannes Sixt wrote:

Show 13 quoted lines

> Am 27.03.26 um 00:37 schrieb Wesley Schwengle:
>> * `remote.*.sshIdentityFile' and `remote.*.sshOpts'
>>
>> Configuration set on owner/path style. This is to support `includeIf`
>> configuration management. For example, a git-forge that host both
>> employer/client repo's. Eg, `git@gitlab.com/waterkip/git.git' and
>> `git@gitlab.com/corp/git.git' would have something configured as:
>>
>> * `core.sshIdentityFile.*', eg
>>
>>      [core "sshIdentityFile"]
>>        waterkip = ~/.ssh/id_ed25519_me
>>        corp     = ~/.ssh/id_ed25519_corporate

> For this reason, I see little incentive to add complexity to Git that
> achieves the same.

It's a hacky solution where you change the ssh configuration permanently. It breaks copy/paste(s) etc for every forge.

In addition, this is where my need came from: It breaks myrepo's configuration(s) for people if they have to override the hostname in each myrepos config. You cannot simply override the hostname in these situtations because of a local ssh config change.

Cheers, Wesley

-- 
Wesley

Why not both?