Exceeded 1 GB limit, can't push, posting to community is apparently only possible "support"

[Ariel Lighty]

Made a commit that, unbeknownst to me, was large and now I've exceeded the 1 GB limit. So, my repo is read-only. I have cleaned the history locally and removed the large files. But I can't push those changes.

From the docs it seems this issue requires contacting support........

which you can't do with a free account...which caused the 1 GB limit.

Remarkable (that's sarcasm).

Anyway this post is an attempt to get a fix that doesn't require just making a new repo.

[Theodora Boudale]

Hi Ariel,

I ran a garbage collection on your workspace's repos, but I'm afraid that the total workspace storage remains over 1 GB.

You can do one of the following two things:

• If you have a clone of the repo locally, with all the branches, but without the large commit, you can delete the Bitbucket Cloud repo, create a new empty one, and then push to it from your local. Please keep in mind that with this approach you will lose any metadata (e.g. pull requests, adjusted repo settings).
  
  
• You can temporarily upgrade to a paid billing plan, make use of the 30-day evaluation period in order to restore write access and push the cleaned history to the repo. When someone upgrades the billing plan of a workspace to the Standard or Premium plan, we offer a 30-day evaluation; if they downgrade to the Free plan before this period is over, we do not charge them. A temporary pre-authorization hold of USD 10.00 is placed on the credit card upon upgrade, but this will return to the credit card within 3-7 days.
  
  If you go with this option, the remote repo will need another git gc after you push the cleaned history. You can leave a reply here and I can run it again for your repo.

Kind regards,
Theodora