If you want a terrible time, have several members of your team not install git lfs, and have them be the main people that commit binary files. LFS uses some so

If you want a terrible time, have several members of your team not install git lfs, and have them be the main people that commit binary files. LFS uses some sort of internal filtering and tracking to determine which binary files might have changed. It seems to have trouble deciding if there are actually dirty files that need changed. So you can't just say, "Okay, go find all the binary files that didn't actually get moved to LFS and correct them" Instead you end up with random moments where you want to commit a single file and git instead detects 1000 png files that it absolutely could not go on without doing something about. But then the diff is a disaster so good luck understanding that what it is actually mad about is that it wants to move the files into LFS. The only way I finally figured it out was to manually load the object blob and notice one of them was an LFS pointer file. I personally think git annex handles things more elegantly, but lfs won that battle.