I dont have an example of that… yet, but it’s definitely in line with what I’ve been planning to write, though my use-case is “just me” and a general preference to save history here into git. (sometimes going so far as to create reconstructed git histories from files found in normal backups!). I had similar thinking of “run from cron regularly, and commit if there have been edits, but a sufficient delay since the last edit to indicate a “session” of editing is likely done”
The part of my git workflow I HAVE been very happy with, is my git-automsg.sh script, which generates a git log with the summary counting the changes, and body of the log listing each file and it’s new/deleted/modified/renamed state - it makes a nice automated git log message, and my TW/node helper script effectively just runs git add * && git commit -a -m "$(git-automsg.sh)
git-automsg from: GitHub - nemothorx/neon-git: nemo's various git helper scripts
In terms of triggering git from client-side - I recall David Bovill talking about that during the Hitchhiker’s Guide to Wiki zoom meeting back in March (Invitation to a Hitchhikers TiddlyWiki All-nighter), so I know it’s doable, but I dont know if it’s public or usable