DevOps Interview DropBeginner TierScenario+10 XP on read
A Git repository has become huge and cloning takes 20 minutes. What would you investigate?
Core Summary
Measure before you guess. Find the biggest objects in history, because size usually comes from binaries and build artifacts committed long ago. Deleting them today does nothing: the old blobs stay in history until you rewrite it or route developers around downloading them in the first place.
Hints
Hint 1: Repo size is history size, not working-tree size
Hint 2: Find the big objects before choosing a fix
Hint 3: Deleting a file today does not shrink the clone
Reported in interviews at Microsoft, Unity