A Bitbucket Cloud Free workspace I administer has become read-only after reaching the workspace storage limit. A small Git push is rejected with a message that the workspace is over the limit.
One repository is substantially larger in Bitbucket’s repository-size listing than an estimate of the Git objects reachable from its known branches and tags in an existing local clone. I realize local and server-side accounting can differ, and there may be references the local clone cannot see.
What is the recommended way to check whether retained pull-request references or unreachable Git objects are contributing to the reported size? If server-side garbage collection is appropriate, how can a Free-plan workspace request it? I can provide the workspace and repository identifiers privately to Atlassian staff if needed. I would prefer to preserve existing branch and tag history.
