Question

A team's Azure Repos Git repository has grown to several gigabytes because designers have committed large .psd and .png files directly into history for the past two years. Cloning now takes over 20 minutes. The team wants to move these existing binary files (including all historical versions) into Git LFS so future clones only download the LFS pointers and current blobs. Which approach correctly converts the existing history to use Git LFS?

Accepted Answer

Run 'git lfs migrate import --include="*.psd,*.png" --everything' to rewrite history so the matching files in all commits are stored in LFS, then force-push the rewritten branches.

Answer

Add a .gitattributes file tracking *.psd and *.png with LFS, commit it, and push — existing files will automatically be relocated to LFS storage.

Answer

Enable Git LFS on the repository in Azure DevOps project settings, which retroactively moves all binary blobs to LFS without changing commit history.

Answer

Run 'git lfs track "*.psd" "*.png"' and then 'git gc --aggressive' to compress the existing binaries into the LFS store.