Commits will have new hashes

Be prepared for things to break.

Historical commits will remain untouched (e.g. 1.0 stuff), but anything after I started keeping the .sketch file will necessarily have a different hash.

This will likely break some things which rely on commit hashes to work. Thankfully, the old (bloated) commits will still exist on GitHub's servers, so anyone pinning their package manager to a specific commit will keep receiving that commit as expected.

Package managers pinning to a specific version (or version range) will likely keep referencing the commit they resolved, until/unless they need to search for a newer version or their caches are purged.

I'm sure there's some GitHub-specific tooling which won't work as expected after the tags are changed over to point to different commit hashes. Pull requests and such should still point to the old (bloated) commits, so their historical usefulness shouldn't be affected.

---

Original issue text

Right now there's a lot of demo images in here which are taking up a lot of space. Might should move those somewhere else, because right now a shallow clone costs over 80MB.

I'd probably go for keeping the images on postimg, but unsure what to do with the Sketch document