Hello Bitbucket Cloud Support,
Our Free workspace remains over its 1 GB storage limit after an oversized commit was successfully removed from the remote branch history.
Verified cleanup and diagnostics:
- The remote branch was rolled back successfully using an exact force-with-lease. The other 15 remote branches were unchanged.
- A fresh mirror clone from Bitbucket contains all 16 advertised branches and occupies approximately 204.47 MiB of Git packs. git fsck passes, and the removed large commit is absent from that clone.
- Bitbucket still reports approximately 845.45 MB for the repository.
- All 427 Git LFS objects uploaded during the attempted recovery have also been deleted. Both repository and workspace UI now show no Git LFS files; reported LFS usage is zero.
- At 2026-10-23 23:12 UTC, a diagnostic push with only a 278-byte empty commit, no new files or trees and no LFS transfer was rejected with the workspace-over-1-GB message and pre-receive hook declined. No diagnostic branch was created and the existing remote refs were unchanged.
Could an Atlassian staff member open a private support ticket, inspect retained server-side objects/references, run repository garbage collection/repacking where appropriate, and recalculate workspace storage usage?
Please do not delete pull requests, other repository metadata, or additional branches without our separate agreement. We can provide the private workspace/repository URL, exact commit IDs, and diagnostic receipts in the private ticket. We are not requesting a paid-plan or trial activation.
Our timezone is Europe/Tallinn (UTC+3 on the test date).
Thank you.
