While there is existing discussion on trying to prevent LFS from keeping two copies of files (#1969 and #2147), running git lfs prune automatically could mitigate the issue for most users.
One way to do this right now is to add git lfs prune in the pre-push hook, but that's inconvenient. Adding an option to automatically do this would be more user-friendly. Thoughts?
While there is existing discussion on trying to prevent LFS from keeping two copies of files (#1969 and #2147), running
git lfs pruneautomatically could mitigate the issue for most users.One way to do this right now is to add
git lfs prunein the pre-push hook, but that's inconvenient. Adding an option to automatically do this would be more user-friendly. Thoughts?