The asphalt --dry-run command is meant for usage in CI, and it errors when there are changes in assets. But, if you use Git LFS and don't pull down the files before running that command, it won't work: it'll compare the hashes of the bona-fide asset and the pointer file, which is obviously always going to be different.
I was thinking through some introspection we could compare the hashes inside the LFS pointer files. But... those hashes are sha256 and we use blake3.
So, a potential solution is to detect Git LFS files, store pointers in the lockfile, and compare those.
The
asphalt --dry-runcommand is meant for usage in CI, and it errors when there are changes in assets. But, if you use Git LFS and don't pull down the files before running that command, it won't work: it'll compare the hashes of the bona-fide asset and the pointer file, which is obviously always going to be different.I was thinking through some introspection we could compare the hashes inside the LFS pointer files. But... those hashes are sha256 and we use blake3.
So, a potential solution is to detect Git LFS files, store pointers in the lockfile, and compare those.