New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Resolve GitLFS breakages #209
Comments
@j-t-t @shreyapandit @alicefeng The symptom of this problem is that git reports the city-specific archives in data_zips have changed when trying to swap between branches, even though no changes have happened in those files. This thread is a couple of years old now, but it seems to pretty closely describe the issues we're having. Suggested remediation when you hit this issue is:
If you get through all that and are still experiencing issues let me know. Thanks. |
It's possible that we may need to resort to using git lfs migrate to fix commits that have already been pushed, but I'd like to hear if the above ideas help others first (they haven't worked fully for me). |
Following those steps enables me to switch branches without encountering the error I had before. However, it still shows that I have modified those files (regardless of what branch I'm on), and when I try to do a git checkout on them, I get |
I can't say for certain but it sounds like at some point the zips have been committed without LFS being used. The way to fix this looks to be using the migrate subcommand I linked to above, here's the gist of it:
Force push has always made me a little nervous, but I expect it's what we need to do in this case. Unless we decide now that git LFS isn't working for this project and we want to look at other options. What do you think @j-t-t ? |
Files managed by GitLFS have been removed from the repo and will no longer be used to manage data, for now we're reverting to using data.world. |
No description provided.
The text was updated successfully, but these errors were encountered: