Working with Git LFS Files
When a file matches a pattern that is being tracked by LFS, an LFS tag appears next to the file name in the right panel.
Clicking on the file shows the LFS reference information:
<img src='/img/documentation/git-lfs/lfs-ref.png' email@example.com 2x' class='img-responsive center img-bordered'/ >
Staging and committing LFS tracked files results in the reference files being saved to your local repo and the actual files being saved to your local LFS cache.
Once your repo is pushed to an LFS-capable remote, the reference files will be saved to the remote repo and the actual files will be pushed to your specified LFS server.
Most LFS actions, such as Checkout, Fetch, Pull, and Push will happen automatically as you use the standard commands in GitKraken. However, if you want to use an LFS command in isolation, use the LFS toolbar menu:
Click the arrow on the button and select the desired command. Other than Prune, all of the commands are run by GitKraken via the traditional operations.
Note: Pruning is not automatic. Pruning is considered a destructive operation, so be careful about when you run the Prune command. See the Git LFS documentation to learn more.