-
Notifications
You must be signed in to change notification settings - Fork 151
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
Convert fix external to git-lfs tracking of fix files #14
Comments
Following git-lfs tutorials online:
Resulting contents of .gitattributes file after initial attempt:
Git status of branch ahead of pushing commit back to fork:
|
Submitted git push of commit and observed upload of LFS objects:
Successful push:
Need to test clone now... |
Clone of master branch without git-lfs change (reference for clone output, steps, timing):
Fresh clone of branch ("Filtering content" portion took the longest but was SIGNIFICANTLY faster than cloning fix from VLab):
The git lfs environment info in a fresh clone:
|
I can clone just fine but I don't think we'll be able to proceed with this. I just received this email from GitHub:
I am forced to stop this effort at this time. :( |
Worked with GitHub support to remove the LFS objects and get us back to zero storage. Using Git LFS is definitely a viable option for the GSI fix files but only if NOAA or EMC pay for data packs or a paid plan. Closing ticket until we have more LFS data available to us. |
…nsda_dualresfix Bug fixes and optimizations to the dual-resolution EnVar
This issue is to track efforts to introduce git-lfs to manage the fix files.
Forked GSI repo to my area: https://github.com/KateFriedman-NOAA/GSI
Created branch: https://github.com/KateFriedman-NOAA/GSI/tree/feature/git-lfs
The text was updated successfully, but these errors were encountered: