This is my first question, so apologize for any misunderstandings.
First, I made a mistake and pushed images which are too heavy for the repository, so the space limit was reached.
After that I reset the repository to the commit before the issue happened (reset 21 commits). The I made a rebase dropping the unwanted commits. This would theoretically solve it, because remote master has been reset.
Basically I followed the instructions from bitbucket documentation:
$ git branch no_images
$ git reset --soft HEAD~20
$ git push --force (up to date)
$ git merge --ff-only no_images
$ git branch -d no_images
$ git push origin master <returns error, space exceeded remote rejected>
At this point my commits are a straight line just like before, but the commits containing image folders were removed.
However, my push are always refused, why?
How do I fix it?
Hello @Gabriel Peixoto de Carvalho ,
Welcome to the Community.
I kicked off forced garbage collection in your repository which reduced its size.
GC is an expensive operation so it doesn't run after every push, this is why there's a delay when reduced size is reflected in Bitbucket. However, if you hit the write limit by pushing a huge file, you indeed can't push new commits.
Anyway, now your repository should be accessible. Let me know if that worked.
Hi everyone, We are looking to learn more about development teams’ workflows and pain points, especially around DevOps, integrations, administration, scale, security, and the related challeng...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events