CODEWITHSUNDEEP
gitgitkraken
bytecode77
bytecode77

Reputation: 14860

GitKraken: "This repository requires LFS but you do not have LFS installed"

For a repository on GitHub, GitKraken shows:

This repository requires LFS but you do not have LFS installed. Modifying files that are tracked by LFS could potentially harm your repository. Please visit our support site for info on installing LFS.

Button: Support Site

However, their support site does not mention "Large File Storage". And the largest file is about 4 MB. How can modifying "large" files harm the repository - potentially corrupted binary data?

And what steps are necessary to meet the requirements here?

lfs

Upvotes: 4

Views: 4726

Answers (3)

warreee
warreee

Reputation: 527

I experienced the same problem on macOS. I initially also had lfs installed through homebrew. I solved it by first removing git-lfs with homebrew:

brew uninstall git-lfs

Next I installed it again using the steps provided here on the website of github. I rebooted GitKraken and the LFS tab became visible.

Upvotes: 1

Bernd Kampl
Bernd Kampl

Reputation: 6299

In continuously get the error you reported after every restart of my macOS machine. I need to fix it every time by running

$ sudo launchctl config user path "/usr/local/bin:$PATH"

My resolution is taken from their documentation. The reason seems to be that if Git LFS is installed via homebrew, the path has to be adapted separately for GUI apps.

Upvotes: 2

Edward Thomson
Edward Thomson

Reputation: 78733

However, their support site does not mention "Large File Storage".

It does, on the Git LFS Requirements page.

How can modifying "large" files harm the repository...?

Git stores each copy of each file in the repository. If you have a 4 MB file, that's no big deal. If you have 1000 revisions of a 4 MB file, that's 4000 MB that is stored locally and transferred every time you clone.

Git LFS works by adding a second object storage area for large files, they will only be transferred when you need to check them out. In the actual Git repository, a small "pointer file" with the information on where to retrieve the binaries is stored. So your repository stays small, but you can get the large binaries on demand.

If you try to work with this repository without installing LFS you will (first) not be able to see the actual binary contents, just the pointer file. You will (second) check binaries into the actual repository, instead of the LFS space, every time you try to add content. It will not be "corrupt", but it will certainly not be what the originators of the repository intended.

This should be as simple as following GitKraken's instructions to install Git LFS.

Upvotes: 8

Related Questions