-
Notifications
You must be signed in to change notification settings - Fork 71
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
Git LFS usage #798
Comments
As far as I understand, old commits (before #512) still contain references to LFS. We would have to rewrite the entire history to completely get rid of that which would be quite problematic for existing checkouts. |
Yea, the script would need to export SHA-like tags for at least the release tags but it's not perfect. And this repo has a few tags already 😬 Just flagging this for awareness in case it was an omission. Not sure if it'll become a problem in the future or not. |
Yeah, we are aware but simply didn't want to rewrite history. Should we close this issue for now and reopen when it becomes a problem? |
One "problem" already is the influx of billing warnings in the notifications for org admins. When this moves to |
FYI, upon transfer we got this notification
|
Is this still a problem? |
I don't have admin access in this org, so I can't tell. Someone would need to go and visit https://github.com/organizations/conda/billing/data/upgrade to tell us. If you didn't do anything about it, the LFS traffic is still there and someone is paying for it. |
We did something about it at some point, but I am not sure if we still pull historic LFS data. |
Going to close this as I didn't hear any further from @jezdez or others. |
We're using 1.21 of 1 GB of data storage and 4 of 1 GB of traffic. So this isn't resolved as such, just not breaking the conda org. I'll buy a data pack now to cover for this. |
Done, this is now 50 GB for traffic and storage for the conda org per month. Please let me know if you need more, preferable ahead of time via a ticket in conda/infra so we have a paper trail. Also kind reminder that these resources are shared with all conda org projects. |
Maybe we should add "lfs: false" to the ci pipelines |
This repository is using a lot of LFS storage above the org quota:
I see that #512 tried to deal with this, but the history still has some. Maybe someone still had a local copy and accidentally reuploaded the content with a push for something else.
The text was updated successfully, but these errors were encountered: