jackTabsCode / jackTabsCode/asphalt
Asphalt dry run doesn't work with Git LFS pointers
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 160
- Forks
- 37
- PR merge metrics
- No merged PRs in 30d
Description
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.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the asphalt --dry-run entry point and reproduce the failure using Git LFS pointer files without downloading the assets. Trace how dry-run compares asset hashes and how the lockfile stores them. Done means dry runs handle LFS pointers consistently while preserving the existing hash behavior for regular assets.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, rust
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100