Why not fixing this 6 years old issue ? Pretty sure it is 2-line fix, just run the hook before opening the commit message window and fill it with the COMMIT_EDITMSG content.

No it would be too slow, all git process must run on the server-side

My message posted 2 days ago is still waiting for moderation. Are you able to validate it ?

The main purpose of this RFE is to be able to use SmartGit on an headless server without XServer/ VNC/ Nomachine/ etc.

About VSCode remote extension, you can take look on official docs:

https://code.visualstudio.com/docs/remote/ssh

https://code.visualstudio.com/docs/remote/ssh-tutorial

Quickly, when connected to a ssh server, VSCode becomes an UI and all its command and process (file open, edit, save, parsing, analysis, searching) are done directly on the server using an headless executable (vscode-server) so it is really fast, almost no latency between the UI and the server.

For SmartGit, it would imply having a SmartGit UI process on the client machine and another SmartGit headless process that would communicate with the UI process through SSH.

Another way could be that SmartGit is just an headless process providing access to its UI through an internal Webserver but a native UI is still better for me.

Indeed, that's exactly the feature what I'm looking for.

In fact, I'm currently using VSCode remote extension + GitLens extension to operate on my distant repo using SSH but I don't like having two different workflow. SmartGit is better for branch management.

A "VSCode remote extension" like feature would be great with:
- Auto install and update server when connecting over ssh

-- If distant server is able to connect to Internet then use its own connection for server install/update

-- If distant server is no connected to internet then use our (client) connection for server install/update