Support SSH/config file

07 Sep, '21
Ed

Without 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
ajd

With 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
Maros

When 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
Andrew

Similar to Ed, without this it is not possible to support multiple Bitbucket accounts. Very annoying.

20 Oct, '21
Cristiam

I 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
Larry

Just 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, '22
mb

What 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, '22
Justin

Really 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, '22
Alain Janssens

+1 for me!

13 Feb, '22
Adebiyi Adedotun

I’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, '22
John

This 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

1

13 Apr, '22
Benjamin Heinke

Totally 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, '22
Daniel

Upvote 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, '22
Nick

I 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.

02 Jul, '22
Roobware

This look like a bug in the GUI. In the 'GitKraken -> Terminal' will the '~/.ssh/config' used for the commands. I think, do fix this bug is not a magical black box. And, for subscribers is this a necessary basic function. I hope the GitKraken Dev Guys will fix this :)

08 Jul, '22
Michael

This is FUNDAMENTAL to developer work. I work in an organization that has multiple Github Enterprise repos. We also support OSS repos. The TERMINAL knows how to pull the correct ssh config file... the UI needs to know this as well!

This is a HUGE pain point for me now... I can't even recommend GitKraken to anyone at the moment either.

12 Jul, '22
simon

i cannot believe this is not implemented. completely makes gitkraken unusable. at least state a response why it is hard to implement if so....

21 Jul, '22
Fokke de boer

I really like Gitkraken, but I'm kind of getting forces to switch because this feature is missing.
I use multiple Github accounts and Github doesn’t allow you to use the same SSH key on multiple accounts.
So I have multiple SSH keys for each Github account and added this in the config file.
But Gitkraken apparently ignores the config file...

I REALLY hope Gitkraken will implement this feature! UPVOTE people

30 Jul, '22
74738

Yea gitkraken are too busy developing silly things like their glow boards (there are enough better project management tools out there…). Just focus on making your core product properly before everyone just jumps ship to something that just does the job.

02 Aug, '22
Andrew S

100% Agree this needs to be supported.

I get that you can use profiles inside of GitKraken to specify certs/keys/etc, but then you're trapped within GitKraken, no other tools will work properly, not even the git command line tool.

05 Aug, '22
Nick

I'd also like this feature. Right now I have to hardcode the ip address of my remote host nickname in my hosts file, and then manually update again whenever that ip changes

30 Aug, '22
Pascal

I just learned today that it doesnt work.
Why?

09 Sep, '22
Chandra

Yeah! I just notice Gitkraken cannot use SSH/config file and I cannot use it for our custom SSH port repository.

19 Sep, '22
Emre

This is a pretty important missing feature :[

Use case (using multiple GitHub accounts):

# Personal GitHub
Host github.com
HostName github.com
IdentityFile ~/.ssh/personal

# Work GitHub
Host github-work
HostName github.com
IdentityFile ~/.ssh/work

07 Oct, '22
Johnny

It's silly that GitKraken doesn't understand the SSH config. What kind of lame system is this? Do you expect HTTPS authentication everywhere?

I use SSH configs to get strong cryptographic authentication and easy aliases:

```
Host github
User git
HostName github.com
Port 22
IdentityFile ~/.ssh/id_ed25519.github
PreferredAuthentications publickey
```

All my repos are cloned via `git clone github:MyName/MyRepo.git` and the command-line tools perfectly handle the keyfile (which is password-protected by the way, so that I Have to enter a password the first time I use a keyfile per computer reboot).

GitKraken on the other hand goes "hurr durr, what is "github:"?"... It's a shame.

I love GitKraken fo managing the history, but I literally have to open a terminal and "git push" because GK lacks this basic Git authentication feature.

Like other people said, please stop developing useless project task managers and work on core Git features first! :D

21 Oct, '22
Tucker Downs

please correctly invoke ssh so that it utilizes the config file. Should be so obvious. Don't know why GK can't figure this one out.

31 Oct, '22
Chris Abernethy

I'm just coming to GitKraken after having used sourcetree for ages. Lack of support for git config and worktrees are preventing me from fully moving to GitKraken at this point, but I look forward to these being implemented as the software itself looks great.

04 Nov, '22
Garrett Sullins

Axosoft, based on the number of comments, can you at least chime in and provide a reason not to support ssh's config file? Without seeing acknowledgement or a comment, it is as if this is no concern to you. As a paid subscriber, this is very disappointing. As most professionals, I have personal and professional bitbucket and github accounts. I love your product. It is an execellent repo tool. However, without the ability to push in gitkraken, I'd rather use tig in the terminal. Although I cannot push using tig, it is a super quick exit to push from the command line. As any busy professional, I prefer quick paths in my tool chains and workflows. Having to leave gitkraken to find a terminal is quite cumbersome.

17 Nov, '22
Kevin F

I hope to see it soon! Perfection is not far!

Good luck :-}

22 Nov, '22
Graham

This would be my number one request.

06 Dec, '22
Brian

+1 for me!

16 Dec, '22
Jan Wesseler

+1 for me too!

03 Jan, '23
Alex S

I have also just bumped into this - I primarily use GK as a visual tool for looking at branches and merges etc. But, it would be great to use the new workspace feature to do a 'fetch all' on a whole ton of repos, but I can't because they require a different GitHub account and therefore custom SSH config...

Supporting the SSH config file is a must!

04 Jan, '23
Nath

+1 from me too :) I also use several ssh keys using the ssh config file, and glad to see I'm not the only one.
I'm pretty comfortable with the command line, but I love the pretty colours of the git hub lines xD

I have only just realised this issue when my PRO trial ran out. And then I couldn't view my public repo anymore with gitkraken as it said it was private.
I assume this is because I was using a custom alias for github to force my ssh to use the correct ssh key.

Using gitkraken's own SSH key to clone the repo fixed this, but shouldn't have to be the fix, as that SSH key won't be reusable on other github accounts

10 Jan, '23
H

I'm evaluating this supposed game-changing 9.0 release, wondering what it would give me that I don't already have with JetBrains, VS Code, and SourceTree.

Evaluation done. Hard pass. Cause of course we use multiple SSH config entries for multiple GitHub accounts.

23 Jan, '23
Anthony

+1 for me, this is essential

29 Jan, '23
Eric

This is essential and basic functionality. Profile switching is a workaround, not a solution - especially for organizations supporting multiple discrete teams or brands each with their own repository. Gitkraken already supports use of the local ssh agent, so the fact that it doesn't respect the config file of the local agent is a non-starter.

30 Jan, '23
Luiz Franco

This feature would make my life so much easier. +1

03 Feb, '23
Savani

+1 It was not an issue in the beginning, I wouldn't mind switching keys, but as I dive into a more complex git workflow it's becoming critical to have that feature.

15 Feb, '23
Jon H

Can’t use Gitkraken over here at Amazon or AWS because of this issue. I would be thrilled to see this feature!!

16 Feb, '23
Daniel DS

+1. This has caused issues for us, especially when using in WSL. We were able to implement a workaround but it's janky and doesn't always work. We'd much rather have support for this feature out of the box.

14 Mar, '23
Alex

+1 from me. I sadly plan to move away from GK just due to this one... Everything else fits my needs.

20 Mar, '23
Adam

+1 As a DevOps engineer I touch 15+ repos on a daily basis, everything from public GitHub repos to private on-prem GitLab repositories only accessible via a SSH jump host. Setting up a SSH config file to reference the various keys, jump configurations, etc. allows me to use the git CLI perfectly fine.

In GitKraken (GK) things are more difficult. Accessing GitHub is trivial through the built-in integrations. However because GK does not support SSH config files, I am required to open the terminal sub-pane and manually enter git commands for the GitLab repos. This causes the GUI to get out-of-sync with the state of the repo and can cause confusion.

TLDR: Implementing this would very much help those of us who deal with different repository hosting services.

20 Mar, '23
Stonesoft

+1. I plan on moving to another solution if I have to keep doing a git push from the CLI after I do anything in GitKraken.

22 Mar, '23
dephinera

+1
This is definitely needed as all of our repos are accessed via ssh with a custom port.

02 Apr, '23
Jame

Any news ??

24 Apr, '23
Sean

Our company uses different ports for off-premises repositories. SSH config seems to be the way we can a address this which rules out using Gitkraken for anything other than local changes.

So for now I'm using my personal Gitkraken account for limited company tasks. I'd love to encourage Gitkraken as a coprorate tool but I can only do so if it works fully.

25 Apr, '23
Michael

leave gitcracken, cant use if without this feature :(

11 May, '23
Chandra

I was able to do git basic operations from terminal because gitkraken not support SSH/config file.
Our companies use custom SSH ports for our git repository.
Usually, I will delete the remote branch from the Pull Request button, and call `git fetch origin --prune` and then delete the local branch from the gitkraken UI.
However, after the recent update (maybe back several version before), everytime I click delete the branch, it will not respond until the git operation timeout.

[Mon May 08 2023 12:12:26 GMT+0900 (Japan Standard Time)] Delete Failed: refs/heads/feature/branchName: failed to connect to xxx.com: Operation timed out

It's not happening in previous version, it will waiting until timeout in the background and not blocking the UI Thread.

18 May, '23
Juhani

+1 for this feature.

Support SSH/config file

Comments: 57