dsh-github-sync

You run dsh on three machines, pick up where you left off on a laptop, spin up a fresh session on the office desktop — yet those sessions, plugin manifests, and settings only live in each box's local directories. Lose one machine and it is gone. dsh-github-sync does one thing plainly: sync dsh's sessions, plugin manifests, and settings to a private GitHub repository so that any machine running the same plugin can read and restore them.

The key difference from earlier git-binary-based sync tools is the transport layer: everything goes through the GitHub REST API, so you do not need a local git installation — sandboxed or minimal environments work out of the box. Each machine writes only to its own instances/ directory in the repo, which means there is no shared file, no merge, and no silent overwrite by construction. Incremental sync is content-addressed (sha1 comparison), so unchanged sessions are never re-uploaded. Restore supports the whole machine, a single workspace, or a dry-run preview, and includes workspace remapping so that a project path differing across machines still lands in the directory dsh actually scans. The three content groups (sessions, plugins, settings) are independently toggleable; turning one off neither uploads it nor deletes the remote copy.

It is built for people who use dsh on multiple machines but do not want to be tied to a git workflow: a dev box, a sandbox, a CI container, a work Mac plus a home PC — as long as you have a private GitHub repo and a fine-grained PAT, install the plugin, fill in the config, and you are done.