![]() So then you can only understand the LFS indicator by also looking at the tracking status column and reasoning that "if there's no indicator and no tracking status then it's misconfigured but if there's an indicator and no tracking status, then it's fine". If it's only for untracked files, then you can't tell the difference between a file that's modified and a file-type that's misconfigured. This is just as dangerous as not having it. It's the same, except that I profusely disagree with the idea of being only "for untracked files". The feature simply indicates whether the file name matches a mask in. There should either be an indicator next to files that will be upload with LFS, or a column with the LFS status, that can be enabled. SmartGit is hiding the LFS status too much. I have half a dozen repositories that now have very large files on the normal Git side, which will never, ever leave the repositories. gitattributes, and going forward, this file type is now handled.īut the damage is done. Over and over, I accidentally put some 30 MB file into the normal repository, because it's some new executable or data file with a new extension, and I don't realize that this extension isn't already in. But without an indicator, it's not immediately obvious that you're committing such a file. SmartGit should show an LFS indicator next to each file that *will be* committed with LFS, *before* the commit is done.Įver so often, you bring in a new file type that should be handled with LFS.
0 Comments
Leave a Reply. |