The workaround for me was to set up the session correctly with the environment variable GIT_SSH_COMMAND, like so: export GIT_SSH_COMMAND="ssh -o IdentitiesOnly=yes -i ~/.ssh/my-secret-identitiy"Īnother thing to note here is that setting the environment variable correctly can be a hustle, so I'm using the command prompt modification facilities provided by things like Liquid Prompt or Fish Shell to hook into the shell and keep updating the environment variables according to the current directory and some rules. In my scenario, similar to Smith scenario (whose solution, BTW, didn't work for me), I need to use different keys for the same server under different repositories. : see my other answer for a configuration-based method with a ready-made script for you to use
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |