Request: manual Git LFS garbage collection for a Free-tier repo (orphaned objects after filter-repo

[svleest]

Hi all,

I run a small private repo (squishlogic/jigsawgeo and squishlogic/ant) on a Free-tier workspace with the 1 GB Git LFS storage limit. I recently used git filter-repo to remove a large directory of reproducible/fetchable assets from the entire git history (all branches), which is the recommended way to shrink history when files shouldn't have been committed in the first place.

After the rewrite and force-push, the pointer files are gone from every branch, but the underlying LFS blob content is still sitting in Bitbucket's storage; my usage didn't drop at all. I understand this is expected: git filter-repo only rewrites local git objects, it has no way to talk to Bitbucket's separate LFS blob store, and Bitbucket's own garbage collection only kicks in automatically once a repo crosses roughly 75% of its LFS quota.

I've been manually finding and deleting orphaned objects through the repo's LFS file-management UI (Settings, Git LFS), which does work and reclaims space immediately, but there's no bulk operation there, no way to sort/filter by "unreferenced," and no listing API I could find to script it, so at real scale (~2,000 leftover objects, ~300+ MB) it's an enormous number of one-at-a-time clicks.

Is there any way to request a manual/server-side garbage collection pass for LFS on a repo, the way it presumably happens automatically once a workspace nears its quota? Or alternatively, is there a supported bulk-delete or list API for LFS objects that isn't documented in the main API docs? Free-tier support only routes me to Community/docs for this category of issue, so I'm hoping someone here (or an Atlassian team member who monitors this forum) can point me in the right direction.

Thanks for any pointers.