(Automatically) commit, but don't push

[inktrap]

What about this usecase: you want to keep an editing history in git, but don't want to push it to a remote? How about two settings:

• enable push (if a URL is configured)
• automatically commit (maybe with some condition, like the edit was ~3s ago and a new file is edited, so consecutive edits of the same file are in one commit?)

I know I can just ignore the git-push error message but it seems inflexible to force pushing. Also I know that there is https://github.com/gitwatch/gitwatch/ which would just automatically commit. But I still think the plugin would benefit if it supported more use cases.

[haydenull]

I think the build-in version control feature of logseq can meet your needs.

[inktrap]

Oh this is great … I saw the setting for this at some point, then didn't enable it, then attributed it to the git plugin and was surprised it was "not available" anymore ;D. I will test how well this works for me and in case it doesn't I would re-open the issue?

Or I can keep it open in case you think splitting commit and push is still a desireable idea for this plugin?

[haydenull]

I think this feature can be added as an optional configuration item to the plugin.
Therefore, we can keep this issue in an open state.