Web interface should update LFS files when `.gitattributes` changes
Problem
When upload, multi-file upload or a rename causes changes to .gitattributes it is possible that files need to move to/from LFS.
E.g. If someone uploads a new .gitattributes file we might need to move all existing .bin files to LFS. If they remove such a file we might need to download all LFS files back into the repo. If the glob for a rule is changed we might need to change some each way.
Solution
We might need to detect changes to .gitattributes and use that to alter how we store other files in that commit. Additionally we may need to schedule the migration of existing files which either no longer need to be in LFS or now need moving to LFS.
Alternatively we might warn against or prevent changes to .gitattribues from the web interface.
Related
Edited by James Edwards-Jones