这是一个很好的做法来分开：

• 代码管理（包括提交行为，在你的情况下，不应该在每一个 li>
  

我甚至可以跳过将它发送到远程git服务器，我只想在本地计算机之间同步文件和开发服务器。

这是一个发布管理过程，就像有一个定期执行rsync的cron作业一样。但它与你的SCM（这里：Git）没有任何关系，它不会有一个原生的解决方案。

I'm developing some software that requires me to use a remote server for testing if it works. I can't host a local version.

Anyway, I have git set up. The way I work right now is I will change something locally on my Windows-based laptop, add a small git commit like "Fix", push it to the remote repository and then fetch it on the development server ( which runs a linux without GUI ).

I don't want to do that becase:

• The git history is littered with small pointless commits.

• It's tedious to have to create comits, push them to the remote repo and then fetch them from the developer server.

So I'm wondering - how should I set up the environment so that any change on my local laptop, even without commiting anything, make the files on the development server change instantly? Is there a way to do it? I can even skip sending it to the remote git server, I just want to sync files between my local machine and the development server.

Best regards

It is a good practice to separate:

• source code management (including the act of committing, which, in your case, should not happen at every little change)
• release management (packaging and deployment)

I can even skip sending it to the remote git server, I just want to sync files between my local machine and the development server.

That is a release management process, like having a cron job doing regular rsync. But it has nothing to do with your SCM (here: Git), which won't have a native solution for that.