Git LFS budget exceeded

[DaniGabana]

Select Topic Area

Question

Body

Hi, I have recently created a new profile and a new organization and I have created a couple of new repositories. The project I have in one of them is 1.7GB aprox so I installed and "activated" Git LFS. However, when I try to push to this repo, i get the following error:
batch response: This repository exceeded its LFS budget. The account responsible for the budget should increase it to restore access.

I had a look at how to increase the budget for LFS but I cannot see the Git LFS Data section in my Billing tab in my organization profile (link below). Is it because I made this organization just a few days ago? I am just asking because I am in another organization and I can see the Git LFS data section if I log in using that other organzation....
https://docs.github.com/es/billing/managing-billing-for-your-products/managing-billing-for-git-large-file-storage/upgrading-git-large-file-storage

The only options I can see when using this new organization is to upgrade to a Teams or Enterprise plans. Is this the new purchasing models Github has? Is there no option to upgrade only LFS if you don´t have a Teams or Enterprise plan (i.e. you are on a Free plan)?

Thanks!

Daniel

[aybarska]

Hi @DaniGabana ,

• Go to your repo settings.
• Scroll down to the archives section.
• Check on the checkbox of Include Git LFS objects in archives.
• Then try to push from locally again.

[isaac-aa]

Hello, I have the same problem as @DaniGabana, but your proposed solution does not work. My organization is brand new (free plan), and I have an older one that works without problem... Maybe something is (temporarily?) down, or there has been a change in the git-lfs billing plans :(

[PeterBeerman98]

I have same problem, just created new org and I cant push LFS files even though I have LFS enabled in repo and spending limits setupped in ammounts that should easly allow for push...
It might be something with the way they changed the entire Billing tab for new orgs.

[roschlau]

Having the same issue. New, free organization, new repo with just a couple of LFS files that should easily fit into the included bandwidth and storage documented here: https://docs.github.com/en/billing/using-the-new-billing-platform/about-billing-for-git-large-file-storage
And I can't even try if increasing the budget for LFS would work, because it says that I need to add a payment method to do that, but I already have a credit card setup ready to go. Something seems broken there 🧐

[Yan-ni]

Having the same issue here too with a new free organization.
Even after deleting budget alerts in the settings or increase them with a payment method configured it's still not letting me push.
At this point I think it's just impossible to use git lfs on a free plan.

[Fyb3roptik]

Same issue for me. I have tried removing budgets but still cannot push. This is really hindering production!

[nandor23]

Is there any update? I am in a similar situation, Usage shows up on one of my older organizations, but not on the newer one. Buying the Pro plan did not solve the issue.

[Yan-ni]

Hello, The issue is fixed for me.

I had the same issue as everyone in here: a new organization but couldn't push any gut LFS to it.

I tried everything, I tried removing budget limits, I even tried to increase the budget and nothing worked but after I contacted the support they get back to me telling me that the budget team had a bug and that they fixed it and that it should be fixed now which was true I could push my git lfs right after it.

[isaac-aa]

In my case the issue still appears (free organization). So maybe the fix is in an per-organization basis or only for paid organizations...?

[SteveSwink]

@Yan-ni can you clarify? Is your organization paid? And how did you contact support? I can't find any way to submit a request; I get bounced back to the useless AI Chatbot every time.

[Yan-ni]

For me the organization is still on the free plan and I haven't changed the budget limit.

I guess contacting the support solved it for me.

Here's the link to create a support ticket to solve this issue: https://support.github.com/contact/account
Make sure to select the right organization when submitting.

[SteveSwink]

Thanks, very helpful! :)

[SteveSwink]

+1 we've migrated a repo to a new Organization account and now cannot push or pull because of "This repository exceeded its LFS budget." Can someone from Github please provide an update on this bug (and a global fix or workaround?) Very annoying!

[isaac-aa]

I have tried again today and I was able to successfully push to the new free organization. I do have the "Include Git LFS objects in archives " option enabled (I had it before and didn't work).

Maybe this was a temporary issue and is now solved?

[rohanmayya]

Having the same issue as this, please fix this asap. I have raised multiple support tickets about this but no response from GitHub team for 4 days.

It is almost definitely a bug with some record in your DB causing this for us -- no matter what card I use and what budget I set for LFS, I get the same error as everyone else above.

We literally cannot push to production because of this!

[isekaiinteractive]

There is no solution. I even reset the history in the hardest possible way because I couldn't reset it locally. I was forced to create a new branch from the desired commit and make it the default, deleting the original dev branch.
Now I still can't pull from remote and also have spaghetti instead of history. Thanks a lot.

I've spent the whole day and all my mental capacity trying to make a build with three features we were working on for the whole week, but nothing worked. All because, for some absolutely idiotic reason, you removed the ability to pay 5 bucks to save me the day. Thanks a lot. From now on, I'm switching to GitLab for all my accounts.

[rohanmayya]

Agree with @isekaiinteractive above. This is actually preposterous -- GitHub just refuses to take my money!

Even if it's a bug on your end, that's OK, if customer support was fast and resolved the issue immediately.

I've left FIVE follow ups on this problem and nobody from support has reached out, let alone fix it. This transition has been very poorly handled.

[zlepper]

So according to these docs: https://docs.github.com/en/billing/using-the-new-billing-platform/about-billing-for-git-large-file-storage#managing-your-budget-for-git-large-file-storage

The default budget for paid usage is $0 for accounts that do not have a payment method on file. For accounts that do have a payment method on file, the default budget is unlimited.

Apparently that is not the case. We apparently just got migrated and everything started falling over left and right because the budget was set to $0 and overspending was not allowed. We usually bought a couple of TB of extra bandwidth each month.

So for anyone else hitting this in the future with org accounts, go into "Billding and licensing" => "Budget and alerts" and then edit the budget for LFS (Or disable the limit entirely which is what we have done for now)

[LBPeterson]

We saw similar behavior today. There was a "$0 budget" set for LFS objects. After removal, the error is no longer happening for our org.

[pnc]

Same here. It looks like something about the new billing migration is botched. (Organization ID is eleostech.)

Error was:

Error downloading object: [scrubbed]: Smudge error: Error downloading [scrubbed] ([sha scrubbed]): batch response: This repository exceeded its LFS budget. The account responsible for the budget should increase it to restore access.

I appreciate you both posting, I didn't realize this was actively being rolled out (on a Friday 🙄)

ETA: Filed as support ticket # 3315494.

[jimsimonz]

thanks that saved me contacting support, just turned on for me today for no reason

[PixelFireXY]

For some reason, the budget was at 0$ after they updated the interface. Thank you, this saved me lots of time

[kristjanvalur]

I was hit by this, and despite tweaking my settings, not able to upload. Then I found this text here:

https://docs.github.com/en/billing/using-the-new-billing-platform/about-billing-for-git-large-file-storage#managing-your-budget-for-git-large-file-storage

Bandwidth and storage usage only count against the repository owner's account. In forks, bandwidth and storage usage count against the root of the repository network. Anyone with write access to a repository can push files to Git LFS without affecting their personal bandwidth and storage usage. Forking and pulling a repository counts against the parent repository's bandwidth usage.

I have added lfs to my fork of this repo. But I can't push anymore, because the original forked repo does not have a LFS budget.

I'm really not sure how to proceed here!...

[JimBobSquarePants]

It's ridiculous that forks eat into a parent repository's bandwidth. Popularity does not automatically mean an increased budget.

[OlegBDA]

Same here, Added LFS Budget, but my collaborators can't clone because "This repository exceeded its LFS budget. The account responsible for the budget should increase it to restore access."
Our project can't go on because of this

[OlegBDA]

Possible solution:
Add payment method and billing info. Add budget for LFS, AND set budget for everything in the Budgets and Alerts. Worked for me, hopefully it works for you too guys.

[OlegBDA]

The "extra" LFS budget in the bottom might be redundant, but I'm too scared to remove it now. If it works, just leave it, right?

[donchuru]

This fixed my issue.
Set a budget greater than $0 for your Git LFS and make sure you put in your payment information.

[jackjansen]

I was just hit by the LFS budget limit issue, on a repo that has existed for a long time, in an organisation that has also existed for a long time. I solved it with unchecking the "stop when budget exceeded", as pointed out above.

But I think there is a real problem with the way this feature is implemented, because I got the error when cloning a public repo:

Error downloading object: Importer/Assets/Scenes/SampleScene.unity (6ba4bb6): Smudge error: Error downloading Importer/Assets/Scenes/SampleScene.unity (6ba4bb647064e63bae95badc79af95cb2b33589e0dbaa29dd6e382d43657f9c7): batch response: This repository exceeded its LFS budget. The account responsible for the budget should increase it to restore access.

To make matters worse this is a repo that contains a Unity Package, normally cloned by the Unity Package Manager, which doesn't show this error in its log, it only shows the dreaded smudge error... I managed to get this message by manually cloning the repo...

This means that anyone external who cloned this repo would also get the same error, with absolutely no way to fix this (because they are not in the organisation that owns this repo). I can imagine that the budget would be enforced for git lfs push, but it seems over-zealous to also enforce it on git lfs pull....

[queenofcorgis]

Hey folks!

Thanks to everyone who wrote in (and to Support), shared workarounds, and kept reporting this.

GitHub has transitioned from spending limits to budgets as part of the new billing platform. Instead of setting a spending limit, you now configure a budget for specific services like GitHub Actions, Codespaces, and LFS.

By default, the LFS budget for non-Enterprise accounts are set to $0.

• The included amounts of LFS bandwidth and storage have significantly increased, you can read more about what’s included in your plan here.
• If your LFS usage already exceeds the new included limit for your plan, you’ll need to edit the $0 budget to allow additional usage:
  Editing a budget
• To estimate your LFS spending, use our calculator
• You can view your account’s current and past LFS usage in the Usage section of Billing, learn more:
  Viewing your Git Large File Storage usage

You can learn more about the new billing platform here:
GitHub’s new billing platform

[dman82499]

Not to mention that these instructions just don't apply any more because the menu options have changed, leading someone to scroll through these comments. I personally tend to completely ignore a thread when the first proposed solution has many downvotes

agreed here, when looking for information about what went wrong I got directed to that page which really confused me, as the instructions no longer work or match the current state of billing. The only way I actually figured out what happened was through here.

[Andrew-Grabish-HypGames]

Welcome to the horror of using a new billing system. We've got a budget set...but if we go back to an old link:

It says we're over budget...can we pretty please get this resolved? I don't want to punch money into here and get double charged at the end of the month.

edit: We just tried to purchase a few data packs to get us over the limit. It says it's purchaed them, the billing page shows no such charges on our payment, the page says we've got an increased limit, but no dice on pulling LFS. We're in a bit of a pickle here. Quite literally all the things are dependent on github working.

[RomanDyriv]

@queenofcorgis There seems to be a bug with Git LFS. We tried adding a budget globally, per SKU, and for individual repositories, but nothing helped. It was working fine yesterday, but today we are constantly facing issues.
This repository exceeded its LFS budget. The account responsible for the budget should increase it to restore access.

[queenofcorgis]

@RomanDyriv and anyone else using this guidance but still encountering issues, please open a ticket on our Support page. Our team may need to look at some account-specifics to get things back on track.

[nlsdvl]

I'm running into this exact issue as well. we updated the organization budget for LFS, we created a budget for the repo specifically, but I'm still getting the error. The repo with this issue is a fork, other repository in the organization using LFS are doing fine. Some information that would be useful in the doc, sorry if I missed it :

• how long does the budget update take to apply ? I suppose immediately.
• if we add a 'per repository' LFS budget, it counts against the organization's global LFS budget, right ? or does it add up to the organization's global LFS budget ? It appears we can create per repo budget that exceed the organization's budget.
• as far as I understand, if my repo is a fork of a repo from another account, then we depend on their budget even if we explicitly configure a budget on my repo. The only option in that case is to detach the fork, is that right ?

[Isak-keycard]

Running into a similar but different issue. We moved an org under an Enterprise. Now the org's budgets should be managed by the enterprise budgets, but since there were budgets on the org level before these are still there. We can't change the org budget because it doesn't have a payment method associated with it, and when we try to add one it says it's managed by the enterprise (which does have a payment method).

[UpgradeEntertainment]

I think this is the worst way to make an update!
I can not address my issue because all the stuff is a mess.
I switch to a pro plan , but my team can not push anything and it says low LFS budget. there is no way to see it, push to init, or get a certain info ! congrats guys! I think you are able to pause tons of projects with one click

[typed-sigterm]

Just a reminder, Pro plan is only for your personal account. If your team uses an organization, the paid plan is Team plan.

[RequieMa]

Billing becomes too complicated to understand.


I chose the simplest but most risky way. I deselected here. I think it is okay if I remember to select it afterwards...

[iamtravisw]

In order to fix this, I had to change my budget from 0 to $1. Even though we weren't using any money from the budget, since 0 was the max and it was at 0, it was causing it to fail. Afterwards, it worked immediately.

[AlexDenisov]

For anyone wondering, it is under "Billing and licenses > Budgets and alerts" https://github.com/settings/billing/budgets

[TimmyBest]

Absolute winner!!! Saved our day!!