Support for Git LFS

[Moulick]

All the files that I have under Git LFS show up as changes

[schacon]

Yeah, it's a good point. We implemented partial support for detecting large files and writing out the LFS format, but we're not reading the setup properly and you can't push to stuff. I can't imagine that GB will work for a repo that needs LFS right now. Sorry about that. It's on our list.

[Moulick]

Thanks. I might add, This repo is not large at all, barely 150 MB in size. We are just following the best practice to keep binary files out of Git and into Git LFS

[jack-foreflight]

Are there any known workarounds for this (in combination with large repos) or is it just recommended to wait?

[nvandessel]

GitButler seems like a very exciting tool, however due to a lot of my work being done in Unity (which necessitates the use of git-lfs) this makes GitButler something I'm unable to use currently.

Unity is also an environment where the use-case for GitButler could be extremely beneficial as it's very easy to make widespread changes, or be working on multiple things at the same time. Would love to see this!

[kjy5]

What's the status of this issue? I'm working on a project now that uses LFS and I'm not sure if GitButler is picking things up. Technically, once the files are in .gitattributes there shouldn't be any new CLI commands needed so shouldn't GitButler just work normally?

[dlavoieb]

How can one add git-lfs to the path of GitButler?

My $HOME/.gitconfig specifies an absolute path to the executable, does GB not parse the config file?

[Byron]

Would you mind opening a new issue for this? This one is about adding git-lfs support, whereas the problem here seems to be a push failing as git-lfs (the binary) can't be launched by Git itself.

In theory, that issue should reproduce even when pushing anything there without GitButler, with git on the command-line.

[davestimpert]

Just to clarify, if I'm using git-lfs, I shouldn't use gitbutler? Or are there work-arounds by doing certain commands on the cli?

[Byron]

Currently, GitButler will not work if filters are used, and from what I can tell no workaround is possible. When gitoxide performs these operations, filters will be fully supported though.

[nickdonnelly]

Just to clarify, if I'm using git-lfs, I shouldn't use gitbutler? Or are there work-arounds by doing certain commands on the cli?

@davestimpert currently you can get around not being able to push by explicitly adding the binary to your PATH on the command line and launching GB from there. On a MacOS machine:

> export PATH=$PATH:/opt/homebrew/bin # <-- This is where my `git-lfs` binary is
> open /Applications/GitButler.app/

[ukarlsson]

Is the best fix currently to delete the hook?

rm .git/hooks/pre-push

[Byron]

If push related hooks are the problem and these are executed by GitButler, in the project settings of GitButler there is a way to turn hooks off.

That might be a less permanent fix as it doesn't involve deleting the whole hook permanently, or prevent it from running when pushing with Git directly.

Push-hooks are executed by the Git binary, which is currently used for pushing.

[davestimpert]

If push related hooks are the problem and these are executed by GitButler, in the project settings of GitButler there is a way to turn hooks off.

@Byron but then the push command wouldn't push the lfs files right?

[Byron]

Actually, I was wrong and have since updated my comment. In short, the UI checkbox only toggles commit hooks. push hooks are still executed as normal by Git.
If it would do that, lfs would be triggered. However, since GitButler currently doesn't support worktree filters, it would probably loose LFS manifests on the way.

[jackTabsCode]

This is highly important to my team as we work in game development with a couple of repos backed by LFS. Would love to see movement on it, as it prevents us from using GitButler at all. Thank you!

[Byron]

Thanks for sharing! There is movement in that realm with V3, but at this point the implementation probably isn't complete enough to truly work with worktree filters (like git-lfs).
It's definitely something we want to have as well.