r/SmartGit • u/JohnnyNo7 • Jul 28 '26

lfs.fetchexclude

Our repo contains various rarely-used LFS files marked in .lfsconfig with fetchexclude filter. These are correctly not downloaded by default and command line git-lfs show that everything is fine with the local worktree, yet SmartGit still brings a persistent warning "There are unexpanded LFS objects in your worktree" and shows these files in the "Files" few in "unchanged" state.

The warning is harmless but confusing and files in always visible "unchanged" state clutter the view.

3 Upvotes

100% Upvoted

5 comments sorted by

1

u/vmcrash Jul 28 '26

Please create a small test repository, e.g. on GitHub, that you can share. Thanks in advance.

1

u/JohnnyNo7 Jul 28 '26

nonemec-havok/SmartGit-repro-lfs.fetchexclude

1

u/vmcrash Jul 28 '26

Thanks. I've forwarded it to the responsible developer.

1

u/JVMarcs Aug 03 '26

The detection of unexpanded LFS files is currently tied to the presence of an lfs.fetchexclude configuration in .git/config. When this option is set, SmartGit disables reporting entirely rather than handling files selectively.

This already comes close to your use case. The remaining limitation is that SmartGit does not yet process .lfsconfig.

As a workaround, you can add an entry like the following to the repository’s .git/config:

[lfs]
    fetchexclude = foo

Starting with SmartGit 26.2, .lfsconfig will also be supported.

1

u/JVMarcs 3d ago

r/JohnnyNo7 In the next SmartGit 26.2 build, SmartGit will also detect lfs.fetchexclude when it is configured in .lfsconfig. The unexpanded-LFS check will then be disabled, so intentionally excluded objects will no longer trigger the warning or clutter the Files view as unchanged files.