ParalleLane does not install the git-lfs binary.
git-lfs must already be installed on your system; ParalleLane handles initialization (
git lfs install) and status display.Diagnosing LFS status and initializing
Check the status in the Git LFS row near the bottom of Settings → ParalleLane → Git.
Diagnosis and initialization are both machine-wide. You don’t need to initialize LFS separately for each repository.
LFS files in a diff
- A file that hasn’t been downloaded shows a Git LFS object card in place of the diff, displaying the file name and size. Use the card’s Download button to download that one file. When you are viewing a past commit, it downloads the file as of that commit.
- A downloaded image displays as the actual image.
- A file that isn’t an image keeps its card after it has been downloaded.
Downloading missing LFS files
When LFS files haven’t been downloaded, a line such as2 LFS files not downloaded appears below the Working copy card in the right sidebar.
Use that line’s Download all button to download them all at once.
The all files tree also shows whether each file has been downloaded.

Locking files
Git LFS locking locks a file on the server so that nobody else edits the same file at the same time. Right-click an LFS file in the Working copy panel or the all files tree, then choose Git LFS → Lock File. To release a file you locked, choose Unlock from the same menu. Files locked by someone else don’t get the lock menu.
Lock: mina-park.
A file with the lockable attribute in .gitattributes shows an open lock icon while it is unlocked.

Bitbucket Cloud repositories don’t support LFS locking, so the lock menu and lock icons don’t appear.
The LFS badge
- Changed file lists show an LFS badge to the right of the file path in commit details.
- Project sidebar shows the badge on the row of any repository whose
.gitattributeshas an LFS tracking rule (filter=lfs). The same is true for a submodule row that has been registered as a child repository, covered in Submodules.

