Support SSH/config file
As a user with multiple accounts set up in ssh_config, I want GitKraken to support this properly.
GitKraken doesn't seem to be able to respect the certificate settings in ssh_config the way command line git does. It forces anyone with multiple git accounts to switch to the command line for any interaction with these accounts, as GitKraken just hangs indefinitely in these setups.
Comments: 14
-
07 Sep, '21
EdWithout this feature, I cannot use GitKraken for most of my repositories, since I have multiple bitbucket accounts, and it is impossible to do that without using ssh configurations. I do not know of ONE OTHER GIT TOOL, GUI or Command line, that does NOT support this feature.
I really don't think you folks are naive.. but, the fact that you can't or wont recognize the importance of this feature is increasingly mind boggling.
And -- if one more person suggest I use "profiles" I'll scream. It just shows that you do NOT understand the issue. I'd be happy to 'enlighten you' if that is what it takes.. -
13 Sep, '21
ajdWith companies moving to more complex security mechanisms, using ssh bastions in zero trust environments, SSH configs are ABSOLUTELY necessary. If you do not support this, we will be forced to change solutions, and I believe many other companies as well. I need to use proxies and ProxyCommands, something that cannot be done today if you do not honor config settings.
-
27 Sep, '21
MarosWhen I heard about GitKraken the first time I was sad it didn't have support for .ssh/config, but I was hoping it will be added soon. Right now, most colleagues use GitKraken and recommend it to me, but it's quite unusable unfortunately. Is there a plan in short-to-medium time to include this feature? I am considering whether I should pay for Pro version or wait a bit.
-
01 Oct, '21
AndrewSimilar to Ed, without this it is not possible to support multiple Bitbucket accounts. Very annoying.
-
20 Oct, '21
CristiamI just opened a support ticket because I have this same request. I use several GitHub accounts (the company where I work and my personal account) and GitHub does not allow the same private key to be registered for both accounts, which led me to use the ssh config file. It works very well from the terminal, but being a PRO user of GitKraken and that this does not work directly in the program is very sad.
If you know of another GIt client that allows this task, please share it with me. Thanks! -
25 Oct, '21
LarryJust chiming in here as well. My paid subscription is basically useless as I have multiple clients, and projects, each requiring bitbucket accounts which can only be managed and used efficiently through a proper SSH config file. Hopefully this is available soon!
-
26 Jan
mbWhat do we need to do to make this possible? This is really nice feature and it missing is really disappointing. Sure hope this is going to be available in short time. i just don't see the point to continue paying for the service.
Best regards! -
28 Jan
JustinReally would appreciate this feature. Was told by support to switch to https which isn't always supported by git remotes. I run my own git server just over ssh and do not wish to add https
-
04 Feb
Alain Janssens+1 for me!
-
13 Feb
Adebiyi AdedotunI’m a new GK subscriber and I badly needed GK, and now it’s unusable for me. Sad. If this doesn't get resolved before my subscription runs out, I won't be renewing. It's also annoying that I've paid for something I basically can not use. It really hurts!
-
17 Mar
JohnThis limitation also means you can't easily use GitKraken with 1Password's new SSH agent.
Docs: https://developer.1password.com/docs/ssh/agent/compatibility#gitkraken -
13 Apr
Benjamin HeinkeTotally agree with everyone. Just got my first client that insists on separated SSH keys. I was led to the SSH config file. But I realized quickly that GitKraken doesn't support it. This makes me question if I renew my license when it expires as it's now becoming a key feature and I see so much use of it. Please do not only consider it but prioritize it. Thank you!
-
04 May
DanielUpvote for SSH_CONFIG support and additionally for shell environment inheritance for things such as local git client environment variables ie GIT_SSH_COMMAND and GIT_AUTHOR ...etc.
I am unable to switch over to GitKraken as my Git GUI without shell environment inheritance or SSH_CONFIG support. As a consultant working on many clients using many SSH keys and GIT_AUTHOR requirements I rely heavily on https://direnv.net/ .envrc files to update my shell environment GIT_ variables based on the parent directory for a client. Allows setting my git author name and email automatically to comply with organization pre-receive hooks. Also setting alternative GIT_SSH_COMMAND such as GIT_SSH_COMMAND="ssh -i ~/.ssh/client2/bitbucket" or similar to override the default keys set in ssh_config for github.com and bitbucket.com. -
16 Jun
NickI hope this gets more traction, and is implemented soon. I will still use GitKraken personally, but for my company, I can no longer use it due to the fact we need to use the `~/.ssh/config` file to point to the correct repository accounts.