SMARTGIT USE SSH INSTEAD OF HTTPS CODE
SMARTGIT USE SSH INSTEAD OF HTTPS PASSWORD

I would say the integration should just allow you to put in a remote ssh connection and a path so something like and then either a password or an ssh key. This process is largely for security reasons, however, the concept is an interesting one. If you have ever used MySQL or another database, you know some clients (SequelPro for example) have the capability to connect via SSH first then connect to the server.

SMARTGIT USE SSH INSTEAD OF HTTPS CODE

What I originally had in mind was not a VS code extension, but more like a connect via SSH.

In that regard, I do use VS Code for coding but do not use their git extension because I think SmartGit works better for me. It is my opinion that SmartGit has the best UI in terms of reflecting the terminology and workflow of the git system, as opposed to some of your competitors. Surprised this is getting traction, but I guess that is how the world works.įor the record, I have been a long time SmartGit user and use the product almost daily. I am the original poster of the comment from four years ago. (I understand about the low priority, but we can dream, can't we?) This ignores when SmartGit directly accesses the file system, but perhaps that's well-capsulated and so could be easily redirected across ssh. The obvious thought is to have SmartGit reach across the network and call git on the remote machine, thus drastically cutting back on the network traffic required. I don't know SmartGit's internals, but it seems to do a lot of its intensive file access by directly calling the git tool. (Separate gripe: tens of thousands of source files, and somehow it's important to have those twelve pairs of files whose names differ only by case? Grrrrr.) Note also that I'm compiling the Linux kernel, which can only be done on a case-sensitive file system, and macOS and Windows are case-insensitive. It's also proximal to the hardware I'm developing for. I'd have to commit and check out every time I wanted to compile. Yes, I could use a local clone, but the remote machine is a monster Linux compile engine with the cross-platform development tools I need. This means that we must go back to caveman days and use command-line git to manipulate files on the remote machine. Even if sshfs is used, the latency to the server makes file sharing far too slow for the disk-access-heavy actions that git and SmartGit use. Remote machines always support ssh, but almost never file sharing.

Smartgit use ssh instead of https