Comment by HexDecOctBin
2 days ago
The ideal behaviour is so have a filter on push too, meaning that files above a certain size should be deleted from non-latest history after push.
2 days ago
The ideal behaviour is so have a filter on push too, meaning that files above a certain size should be deleted from non-latest history after push.
That would prevent old revisions from working... Why would that be ideal?
Why would it stop old revisions from working? What would be the difference between cloning with filter on and delete local versions from old commits?
Cloning with a filter does stop old revisions from working offline. checkout/merge/backfill need to be done to undo the filtering.
At some point, what you're asking for may become a configuration option, likely tied to git gc. It's not there yet because it's all experimental and nobody is paying developers to work on the feature.
I thought you want to prune the destination on push. Pruning local may work for some. It would be extremely annoying for me, because I'm way more likely to dig in old commits than to push. And I really don't want the existing blobs removed without an explicit consent.