Untrack the giant snapfile (2.4GB) #270
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR does the minimal fix needed so that when people clone the repo, they don't suffer a giant 2.4GB download of the snapshot ledger file. I mistakenly added this large snapshot file when I should have created it as a release asset or just had a makefile target to download the file.
The alternatives are:
Option 1 is a bit dangerous and I'll leave that for the future if we strongly need it. So I'll go with option 2 here.
I've also added a .gitignore entry so that the file can't accidentally be committed in the future.