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. — Learn more
% git push --set-upstream origin master --force Enumerating objects: 6798, done. Counting objects: 100% (6798/6798), done. Delta compression using up to 22 threads Compressing objects: 100% (1321/1321), done. Writing objects: 100% (6798/6798), 3.87 MiB | 1.78 MiB/s, done. Total 6798 (delta 5305), reused 6557 (delta 5083), pack-reused 0 (from 0) remote: Resolving deltas: 100% (5305/5305), done. remote: This workspace is over the 1 GB size limit. Reduce the size of your workspace or upgrade to a Standard or Premium plan to increase the size limit. remote: remote: Upgrade to a Standard or Premium plan: https://support.atlassian.com/bitbucket-cloud/docs/manage-your-plan-and-billing/#Change-your-plan remote: Or learn how to reduce your repository size: https://support.atlassian.com/bitbucket-cloud/docs/reduce-repository-size/#Rewind-history-to-undo-large-commits. To bitbucket.org:virus_found/home-configs.git ! [remote rejected] master -> master (pre-receive hook declined) error: failed to push some refs to 'bitbucket.org:virus_found/home-configs.git'
Hello, I confirm that yesterday I tried git-filter-branch to shrink the repo. It did not work and I sent the details in the startning message.
Now I tried BFG. And it did not work either. The remote seems not to be interested in what I am pushing now and what size it is since I once reached the 1Gb limit.
Scanning packfile for large blobs: 7189 Scanning packfile for large blobs completed in 3,040 ms. Found 128 blob ids for large blobs - biggest=559242656 smallest=3202428 Total size (unpacked)=1444502920 Found 1511 objects to protect Found 2 commit-pointing refs : HEAD, refs/heads/master
Protected commits -----------------
These are your protected commits, and so their contents will NOT be altered:
WARNING: The dirty content above may be removed from other commits, but as the *protected* commits still use it, it will STILL exist in your repository.
Details of protected dirty content have been recorded here :
17:21:00 bare/home-configs.git % gs fatal: this operation must be run in a work tree
17:21:31 bare/home-configs.git % git push Enumerating objects: 7189, done. Writing objects: 100% (7189/7189), 97.51 MiB | 7.38 MiB/s, done. Total 7189 (delta 0), reused 0 (delta 0), pack-reused 7189 (from 1) remote: Resolving deltas: 100% (5431/5431), done. remote: This workspace is over the 1 GB size limit. Reduce the size of your workspace or upgrade to a Standard or Premium plan to increase the size limit. remote: remote: Upgrade to a Standard or Premium plan: https://support.atlassian.com/bitbucket-cloud/docs/manage-your-plan-and-billing/#Change-your-plan remote: Or learn how to reduce your repository size: https://support.atlassian.com/bitbucket-cloud/docs/reduce-repository-size/#Rewind-history-to-undo-large-commits. To bitbucket.org:virus_found/home-configs.git ! [remote rejected] master -> master (pre-receive hook declined) error: failed to push some refs to 'bitbucket.org:virus_found/home-configs.git'
Scanning packfile for large blobs: 7189 Scanning packfile for large blobs completed in 3,040 ms. Found 128 blob ids for large blobs - biggest=559242656 smallest=3202428 Total size (unpacked)=1444502920 Found 1511 objects to protect Found 2 commit-pointing refs : HEAD, refs/heads/master
Protected commits -----------------
These are your protected commits, and so their contents will NOT be altered:
WARNING: The dirty content above may be removed from other commits, but as the *protected* commits still use it, it will STILL exist in your repository.
Details of protected dirty content have been recorded here :
17:21:31 bare/home-configs.git % git push Enumerating objects: 7189, done. Writing objects: 100% (7189/7189), 97.51 MiB | 7.38 MiB/s, done. Total 7189 (delta 0), reused 0 (delta 0), pack-reused 7189 (from 1) remote: Resolving deltas: 100% (5431/5431), done. remote: This workspace is over the 1 GB size limit. Reduce the size of your workspace or upgrade to a Standard or Premium plan to increase the size limit. remote: remote: Upgrade to a Standard or Premium plan: https://support.atlassian.com/bitbucket-cloud/docs/manage-your-plan-and-billing/#Change-your-plan remote: Or learn how to reduce your repository size: https://support.atlassian.com/bitbucket-cloud/docs/reduce-repository-size/#Rewind-history-to-undo-large-commits. To bitbucket.org:virus_found/home-configs.git ! [remote rejected] master -> master (pre-receive hook declined) error: failed to push some refs to 'bitbucket.org:virus_found/home-configs.git'
17:21:31 bare/home-configs.git % git push Enumerating objects: 7189, done. Writing objects: 100% (7189/7189), 97.51 MiB | 7.38 MiB/s, done. Total 7189 (delta 0), reused 0 (delta 0), pack-reused 7189 (from 1) remote: Resolving deltas: 100% (5431/5431), done. remote: This workspace is over the 1 GB size limit. Reduce the size of your workspace or upgrade to a Standard or Premium plan to increase the size limit. remote: remote: Upgrade to a Standard or Premium plan: https://support.atlassian.com/bitbucket-cloud/docs/manage-your-plan-and-billing/#Change-your-plan remote: Or learn how to reduce your repository size: https://support.atlassian.com/bitbucket-cloud/docs/reduce-repository-size/#Rewind-history-to-undo-large-commits. To bitbucket.org:virus_found/home-configs.git ! [remote rejected] master -> master (pre-receive hook declined) error: failed to push some refs to 'bitbucket.org:virus_found/home-configs.git'
For that, you have a couple of options to resolve this:
Option 1 - Delete & recreate the repositories This is the fastest way to solve the problem, but loses metadata such as PRs, Pipelines, Permissions, etc.
Perform a clone of those repositories for backup purposes
Delete those repositories from your workspace to free up space and allow you to push. NOTE: This will permanently remove metadata such as PR's/pipelines/user permissions etc.
Identify the largest files in your repositories by executing the following command:
Once complete, push those repositories back to your workspace by creating a blank repository with the same name of the deleted repository, then mirror pushing the contents of the cleaned repository:
NOTE: This will remove metadata such as PR's/pipelines/permissions etc but will keep your commit history and binary files intact.
Option 2 - Temporarily upgrade
Upgrade to a paid plan and utilise our 30-day trial period to restore functionality and provide more time to reduce your repository directly without deletion. You can choose to continue or cease your trial before the end of the 30-day period.
If you encounter any issues during this period - you may raise a ticket directly with our support team using your workspace URL: Atlassian Support
Please let me know how this goes.
Regards, Mark C
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.