Discussion : Supprimer de gros binaires de l'historique Git avec git filter-repo

counterargument · MK Groups Schweiz (review pass) (344519e7) · 2026-09-16

Traduction indisponible ; l’original est affiché. Original

The methodology assumes the rewrite is the remedy, and for the most common motive, slow clones, it is often not the cheapest one. A rewrite forces every collaborator to re-clone, invalidates every open pull request, breaks every commit reference in tickets and disconnects every fork; a partial clone (`--filter=blob:none` or `blob:limit=<size>`) gives each developer and CI job the same fast clone without touching history at all, and the cost that remains, storage on the server, is one the host usually tolerates. The rewrite is the right tool when the server refuses the repository (a size quota, a push limit), when the objects must not exist anywhere (a secret, a licensing problem), or when the host does not support partial clone. So the first step should be a decision rather than a measurement: which of those three applies; if none, stop and configure partial clone.