Hello,
I'm having an issue with Git LFS storage in Bitbucket and would like to clarify how the automatic storage expansion is supposed to work.
Our workspace is on the Standard plan and we have a valid payment method attached to the account. According to the documentation, my understanding is that when the included 5 GB of Git LFS storage is exceeded, additional storage should be billed automatically (e.g. $10 for an extra storage 100GB pack).
However, when I try to push a large Git LFS commit that exceeds the available storage, the push is rejected instead of triggering any automatic storage purchase. No additional charge appears, and the repository remains unable to accept the new LFS objects.
What I would like to know:
1. Is there any additional step required to enable automatic Git LFS storage expansion?
2. Does billing need to be manually activated somewhere beyond simply having a payment method attached?
3. Is there a delay between adding a payment method and Bitbucket being able to purchase additional LFS storage?
4. Are there any workspace-level or organization-level settings that can prevent automatic storage expansion?
5. How can I verify whether my workspace is actually eligible for automatic LFS storage purchases?
Thank you.
Your workspace is on the Standard plan, which has 5GB of included LFS storage.
You're currently consuming 4.8GB of LFS storage, so the extra LFS storage has not kicked in yet.
Once you exceed 5GB of storage, your bill will automatically increase and you will get 100GB of LFS storage - it's not a manual process, it automatically happens. Extra LFS storage is charged at $10/100GB pack:
Cheers!
- Ben (Bitbucket Cloud Support)
Hello and welcome to the Community @Michał Rafacz
The monthly Standard plan includes 5 GB of LFS and should automatically bill you $10 per extra 100 GB.
Check Workspace settings > Plan details to ensure you're actually on Standard (not Free) and that your billing is active with no failed payments.
If everything is correct, it's likely a backend glitch, and you'll need to open a Bitbucket support ticket to have them fix it.
Best,
Arkadiusz 🤠☀️
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.