nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Repo on BitBucket over limit, local has been cleaned of large files, how can I push?

Ricardo Pereira_2rcptc

Hello

I have accidentally uploaded a folder with a large number of files and we have exceeded the allowed limit of 4Gb.

I have deleted the files locally, but I can no longer commit because I always get the same error. I have executed different commands that I have found in this forum, but it seems that none of them work for me,

I think the only thing I need is to run the garbage collector. Can you please help me?

Thanks

Accepted answers

All comments

Theodora Boudale

Hi @Ricardo Pereira,

I can see in our system the repo over the 4 GB limit from the ones that you have access to. I ran a git gc for this repo, but its size remains unchanged.

Could you please let me know what changes you've made to your local repo?

Did you do a git reset to undo the large commit? In this case, you should still be able to push (a git reset of the problematic commit can be pushed even if the repo is over the 4 GB limit)
Did you commit file deletions?
Or did you rewrite history with a tool like BFG or git filter-branch?

In the last 2 cases you won't be able to push, the only thing that can be pushed to a repo over the 4 GB limit is a git reset and no new commits.

Please let me know which of the 3 changes you have made and what is the output of git count-objects -Hv in your local repo so I can suggest further actions.

Kind regards,
Theodora

Ricardo Pereira_2rcptc

Hello Theodora,

thanks for the quick answer.

After the git count-objects -Hv this is the result.

count: 947
size: 5.15 GiB
in-pack: 0
packs: 0
size-pack: 0 bytes
prune-packable: 0
garbage: 8
size-garbage: 1.91 GiB

I have tried to delete files and use the git reset, but did no worked.

Ricardo Pereira_2rcptc

The problem is that on my last commit I forgot to send a Git.ignore file.

I hope this helps with my problem. Thanks.

Theodora Boudale

Hi Ricardo,

The output of git count-objects -Hv shows that your local repo has a size of 5.15 GiB.

If you inspect the history of your local repo:

is the problematic commit (with the large files) still part of the repo's history?
if so, have you merged the branch with this commit to any other branch?

If the answer to both questions is no, you can try running a garbage collection on your local repo with the command

git reflog expire --expire=now --all && git gc --prune=now --aggressive

and then inspect the size again git count-objects -Hv

If the problematic commit is still part of the history, and you have not merged the branch to any other branch, you can check the steps mentioned in the link below on how to undo the last push:

https://support.atlassian.com/bitbucket-cloud/docs/reduce-repository-size/#Undoing-the-last-push

If the answer to both questions I asked before is yes, or if the options above do not work, I would suggest trying to remove the folder with the large files from the repo's history with BFG:

https://rtyley.github.io/bfg-repo-cleaner/

This page provides step-by-step instructions on how to do that. You can use BFG with the argument --delete-folders (mentioned in the link) in order to remove it from the repo's history.

Some important notes about BFG and rewriting history:

Always take a backup of the repo before you proceed with any of the changes I suggested above, in case you accidentally delete something you didn't want to and want to recover the repo to the prior state. You can take a backup by cloning with the --mirror flag (other than the one you will use for BFG):

git clone --mirror repo_url

BFG does a history rewrite. This means that the commit hashes of the repository will change. It's good to communicate this to your team so there are no surprises, and also so that they take a fresh clone of the repo after you push your changes (and avoid pushing the old history back)
After you make changes with BFG, I would suggest pushing them to a newly created repo first, in order to inspect the history and confirm if it looks ok.

When you have a local repo of a smaller size (you can check that with the command git count-objects -Hv, specifically the fields size and size-pack in the output), please let me know, and I can temporarily increase the repo size limit so you can push your changes.

If you have any questions, please feel free to let me know.

Kind regards,
Theodora

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Unanswered
Groups
Help

Find more posts tagged with

bitbucket

bitbucket-cloud