Your workspace has exceeded the 1 GB limit and has been placed in read-only mode. Learn more about upgrading your plan and checking storage usage

By | May 31, 2025
0 Comment
Spread the love

Bitbucket Cloud workspace has hit the 1 GB storage limit (applies to free-tier plans). When this happens, the repository becomes read-only (no pushing changes, no creating branches or PRs, etc.).

How to Fix This in Bitbucket

✅ 1. Check Storage Usage

To find out which repositories are using the most space:

  1. Go to Bitbucket Settings.

  2. Under your workspace, visit:
    Settings → Plan details or https://bitbucket.org/account/settings/plan

  3. You’ll see used vs. allowed storage and which repos are the heaviest.

✅ 2. Reduce Repository Size

You can reduce space usage by doing the following for large repos:

  • Clean large files from Git history using git filter-repo or BFG Repo-Cleaner.

    • Common targets: old binary files, build artifacts, logs, .zip, .mp4, etc.

  • Remove Git LFS files you no longer need:

    bash
    git lfs uninstall
    git rm --cached path/to/large/file
    git commit -m "Remove large files"
    git push --force

⚠️ Force-pushing after rewriting history will affect collaborators. Communicate beforehand.

✅ 3. Upgrade Your Plan (If Needed)

If cleanup isn’t enough or you want to avoid limits:

  • Go to Bitbucket Plan Pricing

  • Upgrade to the Standard or Premium plan for more storage (starts at 5 GB for Standard).

✅ 4. Delete Unused Repositories

If you have old, unnecessary repositories:

  1. Go to the repository.

  2. Click Repository Settings → Delete repository.

  3. Confirm deletion.

🚀 Suggested Next Steps

  • Run: git count-objects -vH to see local repo size.

  • If you need help running BFG or rewriting Git history, I can guide you step-by-step.

Would you like help identifying and removing large files from a repo? If so, share the repo name or du -sh .git and git rev-list outputs.