Gist version history is verbose, change storage format?

[SidneyNemzer]

Github Gists record every change, so the autosave creates quite a lot of noise in the revision history.

Any ideas on how that could be reduced?

My ideas so far:

• Store modified snippets in Chrome Sync storage, only commit to Gist when user manually saves. The simple version of this would only allow 8,000 bytes of snippets to be unsaved. The complex version could shard snippets across multiple top-level keys to allow 102,400 bytes. Problem: sync storage saves and restores from the cloud "when it feels like it", so it's possible that when you switch computers, your changes won't be available on the other computer.
• Periodically combine old commits in GitHub Gists (assuming you can even manipulate the Git data for a gist). Edit: confirmed Gists support cloning, force pushing, and branches.
• Store manual saves on master branch, autosaves on another branch, merge when manually saving. If we go this route, it's probably better to just use a full GitHub repo instead of a Gist.
• Custom storage server. This is the most flexible but it would cost money to host. Maybe I could do something with Firebase? NoSQL/Realtime might not be entirely appropriate though.

[SidneyNemzer]

Update: I confirmed that GitHub Gists support cloning, force pushing, and branches (invisible on the web interface). Probably better to just use a regular github repo though.

Still considering Firebase too. Maybe could stay in the free tier? Might be OK because there won't be much relational data (although that's what I always tell myself before using Firebase and I usually regret it...)