How to push when the repo size is over the size limit?

[Ignacio Mosconi]

Hello, there.

We are having an issue with a repository that has exceeded the file size limit, and no longer accepts pushing more commits. The account that pushes to this repository has already activated the "delete dangling commits when over the size limit" lab feature, and made a force push to undo the latest commit on a branch. We believe that the way to solve this is by running the gc command on your side. Is this correct? Or is there something else we can do ourselves to fix this issue? This is the repo URL: https://bitbucket.org/itrocks-web/not-maev-game-rebase

Moreover, we would like to know if the previously mentioned lab feature triggers the garbage collection when pushing from an external CI system. For instance, we are performing this steps in our automated workflow to prevent going over the size limit each time we make a commit (due to the fact that the repository is being used as a sort of deployment platform for an application, so we don't care about preserving commit history in this use case):

git checkout $checkoutBranch
latestCommitId=$(git rev-parse HEAD)
if [ "$latestCommitId" != "${{ vars.DEPLOYMENT_REPO_HARD_RESET_COMMIT_ID }}" ]
then
git reset --hard ${{ vars.DEPLOYMENT_REPO_HARD_RESET_COMMIT_ID }}
git push --force
fi

After that, we commit and push using:

git add .
git commit -m "Version ${{ ref_name }}"
git push

Thanks in advance for the help.

[Patrik S]

Hello @Ignacio Mosconi ,

Welcome to Atlassian Community! 

I noticed you have opened an internal ticket with us, and a Support Engineer from Bitbucket already manually triggered the GC for your repository, which decreased the size to 2GB.

Just sharing the outcome of the internal ticket, the automatic GC should be triggered when a force push is executed in the repository. However, t if the repository is pushed again with dirty dangling commits from a different local machine, these dangling commits will be reinstated, which will cause the repository size to balloon back up to its previous size.

If you encounter a situation where the automatic GC was not able to clear the dangling commits and reduce the repository size, please feel free to Raise an internal ticket with us and we can manually trigger it for your repository.

Thank you, @Ignacio Mosconi !

Patrik S

[Ignacio Mosconi]

Hi, @Patrik S !

We were able to solve the issue thanks to the manual GC run on your side. Thank you very much!

[Jens Schumacher - Released_so]

Hi @Ignacio Mosconi 

Atlassian Knowledge Base has a good summary of actions you can take to reduce the repository size. 

Hope this helps.

Cheers,
Jens

Released.so - Release notes powered by Jira