I have the following use case: I would like to be able to push to git@git.company.com:gitolite-admin using the private key of user gitolite-admin, while I want to push to git@git.company.com:some_repo using 'my own' private key. AFAIK, I can't solve this using ~/.ssh/config, because the user name and server name are identical in both cases. As I mostly use my own private key, I have that defined in ~/.ssh/config for git@git.company.com. Does anyone know of a way to override the key that is used for a single git invocation?
(另外:gitolite根据键来区分谁在进行推送，所以就访问、所有权和审计而言，user@server字符串对于不同的用户是相同的，这不是问题。)
即使用户和主机是相同的，在~/.ssh/config中仍然可以区分它们。例如，如果你的配置是这样的:
Host gitolite-as-alice
HostName git.company.com
User git
IdentityFile /home/whoever/.ssh/id_rsa.alice
IdentitiesOnly yes
Host gitolite-as-bob
HostName git.company.com
User git
IdentityFile /home/whoever/.ssh/id_dsa.bob
IdentitiesOnly yes
然后在URL中使用gitolite-as-alice和gitolite-as-bob代替主机名:
git remote add alice git@gitolite-as-alice:whatever.git
git remote add bob git@gitolite-as-bob:whatever.git
Note
您希望包括IdentitiesOnly yes选项，以防止使用默认id。否则，如果您也有与默认名称匹配的id文件，它们将首先被尝试，因为与其他配置选项(遵守“first in wins”)不同，IdentityFile选项附加到要尝试的身份列表中。参见:https://serverfault.com/questions/450796/how-could-i-stop-ssh-offering-a-wrong-key/450807 # 450807
以下是简单的方法:
-从你的本地根git文件夹。
-检查当前本地存储库的认证方法类型为HTTPS或SSH。
git remote -v
Example using HTTPS:
origin https://github.com/juantorres9/SQLite_crash_cours.git (fetch)
origin https://github.com/juantorres9/SQLite_crash_cours.git (push)
Example using SSH:
origin git@github.com:juantorres9/SQLite_crash_cours.git (fetch)
origin git@github.com:juantorres9/SQLite_crash_cours.git (push)
-设置您选择的身份验证方法，以防尚未设置。
For setting SSH
git remote set-url origin git@github.com:USERNAME/REPOSITORY.git
For setting HTTPS
git remote set-url origin https://github.com/USERNAME/REPOSITORY.git
-再检查一遍以防你想再次检查
git remote -v
-你现在可以使用你配置的方法来使用git push:fetch。
git push origin master
请注意
最后但并非最不重要的，检查更新的官方文件
https://docs.github.com/en/get-started/getting-started-with-git/managing-remote-repositories
我已经在github上测试了以下方法，基于阅读其他答案，它结合了一些技巧:
正确的SSH配置
git URL重写
这种方法的优点是，一旦设置好，它不需要任何额外的工作来使它正确-例如，您不需要更改远程URL或记住以不同的方式克隆东西- URL重写使它全部工作。
~ / . ssh /配置
# Personal GitHub
Host github.com
HostName github.com
User git
AddKeysToAgent yes
UseKeychain yes
IdentityFile ~/.ssh/github_id_rsa
# Work GitHub
Host github-work
HostName github.com
User git
AddKeysToAgent yes
UseKeychain yes
IdentityFile ~/.ssh/work_github_id_rsa
Host *
IdentitiesOnly yes
~ / . gitconfig
[user]
name = My Name
email = personal@personal.email
[includeIf "gitdir:~/dev/work/"]
path = ~/dev/work/.gitconfig
[url "github-work:work-github-org/"]
insteadOf = git@github.com:work-github-org/
~ / dev /工作/ gitconfig。
[user]
email = work@work.email
只要你把所有的工作reppos放在~/dev/work和其他地方的个人物品下，git在向服务器进行拉/克隆/推操作时将使用正确的SSH密钥，并且它还将为你的所有提交附加正确的电子邮件地址。
引用:
1
2
正如其他人提到的，核心。sshCommand config可以覆盖SSH密钥和其他参数。
下面是一个示例，其中有一个名为~/的替代键。Ssh /workrsa，并希望将其用于~/work下克隆的所有存储库。
在~/work下创建一个新的.gitconfig文件:
[core]
sshCommand = "ssh -i ~/.ssh/workrsa"
在全局git配置中~/。gitconfig,添加:
[includeIf "gitdir:~/work/"]
path = ~/work/.gitconfig
