Our Bitbucket Cloud workspace, otherhalfdigital, is in read-only mode because it has reached the 1 GB workspace storage limit.
The repository otherhalfdigital/wellness-app-2026 is shown as 507.38 MB in Repository settings. We have preserved an offline backup and prepared a history cleanup removing archived source-audio backups and a generated export archive. The cleaned repository packs to approximately 370 MiB, compared with approximately 452 MiB for our unfiltered local history. Its current application file tree is verified unchanged apart from the intended backup/archive removals.
Both an ordinary push and a force-with-lease push of the cleaned history are rejected by the workspace pre-receive hook: "This workspace is over the 1 GB size limit." The cleaned history has therefore NOT reached Bitbucket, and the remote master branch remains unchanged.
Could an Atlassian support engineer run server-side garbage collection on this repository and recalculate workspace storage, to clear any existing unreachable objects? If that does not free enough space, please advise a supported way to submit the size-reducing history while the workspace is read-only, without deleting/recreating the repository or losing its permissions and metadata.
We are not requesting a paid-plan change. Please let us know what further diagnostic information you need; we can provide private details through an appropriate private channel.
