Hi Git developers,
I ran into an issue using `git repack --drop-filtered` in a partial clone repository.
Problem
When a blob selected by the filter for dropping is referenced by the current index, Git aborts the entire repack with:
`fatal: cannot drop 'path/to/large-file.bin' (object-id): it is referenced by the current index`
This stops other eligible blobs from being dropped, even though those blobs are not referenced by the index.
Expected behavior
I’m wondering if Git could skip blobs referenced by the index and continue dropping the rest of the eligible objects, instead of aborting the whole operation.
For example:
Blob A: eligible for dropping, not referenced by index → drop
Blob B: eligible for dropping, referenced by index → skip
Blob C: eligible for dropping, not referenced by index → drop
The repack could complete successfully, optionally emitting a warning for skipped blobs.
Question
Is there a specific reason this condition is treated as fatal rather than skipping the affected objects?
This behavior would be especially helpful for partial clones with large working trees.
Thanks!