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.
