Jamie, Can you mention git Large File Storage?

One of our product's domain-specific file types, "pattern files" is often stored as source code in binary form in our customers' programs. (Our customers use our product to write their own code. They can use Git, too!) The largest single repos can have multiple GB of such pattern files.
- [ ] Does [Git LFS (Large File Storage)](https://git-lfs.github.com/) handle those files seamlessly, as if they were inside the repo?
- [ ] If I change 1 bit in a 1 GB file, does LFS minimize bandwidth during push/pull?
- [ ] Can we hook in a custom diff utility for changes to these binary files?
- [ ] Advanced topic: There's an ASCII equivalent source for these binary files, but the compile step can take 10's of minutes for larger files. (Thus the tendency to store the binary files.) Should we encourage ASCII source storage instead of binary files?
- [ ] Advanced topic: Assuming a repo is storing the ASCII pattern source, is there a CI or Git Action that we can use to automatically kick off our pattern compiler after a pull, but only on any ASCII source file that has changed?