SSH Tunneling

Comments: 19

• 25 Aug, '21
  Matt H

  I just discovered the GitLens and Git Graph extensions for VS Code that almost make this feature request a moot point.

• 09 Dec, '21
  Peter

  I let my GitKraken license drop because this feature is missing. I'd happily subscribe again if I could use GitKraken with my VS Code Remote SSH workflow!

• 27 Jan, '22
  Lothar Wiebusch

  We are waiting for that feature. Out whole develpoment team uses gitkraken and working on remote linus servers should not change anything on that.

• 21 Mar, '22
  Axel Heider

  maybe loosely related to https://feedback.gitkraken.com/suggestions/280386/support-repos-in-a-sshfs-mountpoint

• 28 Mar, '22
  Matt

  We switched over to developing on a remove VM using JetBrains Gateway. Works great so far except the git client is really lacking.
  
  I'm X11 forwarding gitkraken, but it's pretty clunky.
  
  It would be really nice if GitKraken had a native solution for remote environments.

• 13 Apr, '22
  Erik

  I have a very old laptop, but very beefy development machine, so I'm constantly using remote development tools. With JetBrains giving a lot of focus to remote development as well, there will be even less projects I work on locally. It would be amazing if GitKraken could support remote development as well.
  
  The VSCode extensions and JetBrains git tools work, but I much prefer GitKraken

• 08 Aug, '22
  Eyal

  +1 for that, Gitkraken is now out of my dev env. That would be a dealbreaker when coming to renew my pro membership in 3 months.

• 19 Aug, '22
  Ahmed

  +1 fo having this. Dealbreaker and will let me unfortunately let the trial license end without a renewal. Will keep an eye until it get developed and will get license for my team.

• 21 Sep, '22
  Kim

  Hope this feature would be developed

• 24 Nov, '22
  Vladas

  This feature would be very iseful

• 07 Jan
  hud

  Didn't realize this issue was not supported when I signed up for the PRO. Will be discontinuing the PRO until this feature is up

• 14 Jan
  Dan

  Canceling my membership as well unfortunately because of this missing feature. Would happily subscribe again if it is added in the future.

• 17 Jan
  David J.

  +1 "Didn't realize this issue was not supported when I signed up for the PRO"

• 09 Feb
  Mat

  Adding my two cents that I would really like this feature as well!

• 11 Feb
  Serigous79

  Please add this feature. It would support a workflow that many people are now using.
  
  For example: create an EC2 instance on AWS and use VSCode's remote SSH feature to develop code locally via a more powerful machine.

• 13 Mar
  Simon

  I have used Gitkraken Pro for several years now and this is one of the few limitations that I've encountered. Would be great if it would be supported out of the box. This is especially useful in enterprise environments!

• 11 Apr
  Joaquim

  started using remote environment through SSH
  would appreciate having remote SSH git management

• 13 Apr
  Javier

  My department was using GitKraken Pro and after changing to a distributed system workflow via NFS we are not able to use it anymore. I tried several things to improve git performance over my mounted repos.
  I made a git alias to improve git performance by using git in the remote machine via ssh and it worked.
  However, GitKraken uses libgit2 so it is not affected by the installed git in the bare machine.
  
  I tried GitLens with VSC Remote Explorer and works good but has many missing tools. I wasn't even able to edit a commit or even ammend it.
  I'm also abandoning the ship, unfortunately, until this feature is taken into account.

• 14 Jul
  Scott

  As others have noted, application development is happening more and more remotely i.e. "in the cloud" and no longer locally. There are a ton of advantages to doing this and why it is getting more and more popular. Having Git control of a code base remotely is also a necessary part of the "remote development" process.
  
  Some in this and the other similar suggestion have said, "I had to drop my subscription to Gitkraken, because this feature is missing." I'm in this boat too. My team has moved our application development to being remote and thus Gitkraken no longer suffices, because we can't work remotely with it, which is a shame. This can't be that hard.
  
  Please make this happen!
  
  Thanks!
  
  Scott
  
  Here is the other similar suggestion: https://feedback.gitkraken.com/suggestions/223779/repository-management-on-remote-machine-using-ssh-connection