Repository size / quota not decreasing after git push --force following history rewrite #2474

Closed
opened 2026-03-25 00:11:12 +01:00 by LIkus777 · 3 comments

Comment

Hello,

I rewrote the Git history of my repository to remove large binary files (APK ~230 MiB, fonts zip, etc.) using git filter-repo and then pushed with git push --force to Codeberg.

Locally, the repository is now small:

git count-objects -vH reports size-pack ~59 KiB, garbage: 0
Only 2 commits remain on master; the pushed pack was on the order of tens of KiB
Despite that, the repository / account storage figure shown in the Codeberg UI still appears to reflect the old size (on the order of hundreds of MiB), as if unreachable objects from before the force-push were still counted.

Repository: https://codeberg.org/LIkus777/IqraApi
Branch: master

Question: Is this expected until server-side git gc runs on your side? If so, is there an ETA or a way to trigger / request garbage collection for a specific repo? If not, could you advise what else might cause the UI quota to stay high?

Thank you for Codeberg and for any guidance.

### Comment Hello, I rewrote the Git history of my repository to remove large binary files (APK ~230 MiB, fonts zip, etc.) using git filter-repo and then pushed with git push --force to Codeberg. Locally, the repository is now small: git count-objects -vH reports size-pack ~59 KiB, garbage: 0 Only 2 commits remain on master; the pushed pack was on the order of tens of KiB Despite that, the repository / account storage figure shown in the Codeberg UI still appears to reflect the old size (on the order of hundreds of MiB), as if unreachable objects from before the force-push were still counted. Repository: https://codeberg.org/LIkus777/IqraApi Branch: master Question: Is this expected until server-side git gc runs on your side? If so, is there an ETA or a way to trigger / request garbage collection for a specific repo? If not, could you advise what else might cause the UI quota to stay high? Thank you for Codeberg and for any guidance.

I have done the same thing last week, for a private repo. It is 4 MiB now, but it still shows as 100+ MiB here in the UI.

I have done the same thing last week, for a private repo. It is 4 MiB now, but it still shows as 100+ MiB here in the UI.
Owner

It looks to me the size has been decreased now.

It looks to me the size has been decreased now.
Author

@Gusted wrote in #2474 (comment):

It looks to me the size has been decreased now.

yes. because I deleted the repo...and pushed it again.

@Gusted wrote in https://codeberg.org/Codeberg/Community/issues/2474#issuecomment-12496809: > It looks to me the size has been decreased now. yes. because I deleted the repo...and pushed it again.
Sign in to join this conversation.
No milestone
No project
No assignees
3 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Codeberg/Community#2474
No description provided.