The LFS column is definitely empty for me in any view on files that GitKraken is definitely picking up as LFS files, and I'm definitely on 19170.

I wasn't aware of that setting, where do you set it?

But just to make sure that isn't a huge misunderstand, is the LFS stuff you're working on about locks? If so, I've failed to explain that this is purely about being aware of which things will go into LFS and which will go into the repository before the commit. I've never used an LFS lock.

I found it, I didn't realize it live-updated.

But it doesn't seem to work yet. Here is a PNG file, which is in .gitattributes:

And in GitKraken:

Thinking it had to do with a repository not being initialized, I installed LFS on a less important project, and I also couldn't trigger anything in that column.

Hi,

Where are these previews located? The last one I see is 22.1 Preview 13. from 7-28.

Per

Hi,

Good, I'll check it out.

Keep in mind that this icon is ONLY valuable for untracked files. Once a binary file has been commit to the main repository, the irreversible damage has been done. The only time this matters at all is for untracked files, and it should be as loud as possible. A little 5x5 pixel difference in the document icon doesn't solve the problem. This is about preventing the operator from casually making a catastrophic change to the repository that will require a total reformat and loss of all Git history.

Per

I'm not clear on whether what you're showing is a future version or the current version running with different settings.

But it's also too subtle. Remember, this is an op-sec thing. You're not allowed to make one mistake ever with committing LFS files. Having been burned severely and repeatedly, I now have to choose a git client *entirely* based on whether it helps me not accidentally binary files to the regular repository. The SmartGit icons don't help, because they're basically pixel art. This will go wrong over and over and over.

The only thing that will work is a separate column with a big fat icon that says LFS, and GitKraken is one of the only clients that has this. The choice is made for me, I must use GitKraken regardless of what I think of it otherwise.

The question is whether you're trying to support the bare minimum or whether you're trying to be awesome at LFS. If you're trying to be awesome, and if you've used LFS for anything important ever, you'll know that there's a thermonuclear accident hiding in waiting on every commit, requiring a complete reformat of the repository if it happens. The only thing that stands in the way is the pixels showing that you're about to make a mistake. It looks like you're dedicating about 4x4 pixels to it. That's not enough.

I'll check back in a year and see if SmartGit's priorities has changed. The folder view is needed for microservices. This is a major flaw in GitKraken. But otherwise, GitKraken is the only game in town, because they're willing to tell you if you're about to trash your repository. On a game, LFS assets can sneak into every commit. SmartGit is way to quiet about it to be helpful.

It's too bad, it really is.

I still don't see this working. So this is the repository in SmartGit with one unchanged LFS file.

And here's the same in GitKraken:

I can't for the life of me figure out why SmartGit believes that there's now a badge. I've been through all menus many times, and I'm not seeing it.

To be completely honest, I ditched SmartGit for GitKraken, and it's only because of two minuses that I'm still seeing if SmartGit has become friendly to Git LFS, (1) GitKraken is not good for managing a lot of repositories (microservices) where SmartGit has a folder list, and (2) GitKraken's internal Git client requires dual authentication when using LFS.

I still don't understand why SmartGit seems on some religious mission to NOT have this feature. It's so simple, and it's an LFS dealbreaker. Once a large binary file makes it into the main repository, the whole thing is shot. You need to rebuild the repository from scratch and lose all history, and set up all users again. It's a catastrophic omission for SmartGit to refuse to inform people whether files will go into the main repo or LFS. For an LFS user, this is life or death, and SmartGit is categorically off the table for LFS without such a feature.

Per

Was this feature dropped? Testing 22.1 Preview 9 (build 19130), and I'm not seeing any indicators anywhere.

It's great to see you're doing this important feature. However, since you mentioned in the other thread that SmartGit would likely never get this feature because it wasn't upvoted enough, I was forced to make a choice and settle on GitKraken for all my Git work including LFS. And now I've habituated to GitKraken in the meanwhile. So I likely won't be returning. But I'm happy for other SmartGit users doing LFS.

And it's now canceled. It was subscription 249691774. What an ultra-bummer.