Support Git LFS (Large File Storage) locking feature

65 votes

Currently when working with a repository that makes use of the file locking feature (e.g. game development - locking binary files, that can't be merged reliably), GitKraken sadly has no way to interact with the locks.
This means we as sysadmins / CLI capable people have to unlock certain files for teammembers or use an additional tool that does just that like gitlit ( https://github.com/S2-/gitlit ).

It would be great to have file locking integrated, when using the file locking with a lfs repo.

Under consideration Suggested by: Joscha Wülk (30 Sep, '21) • Upvoted: 11 Apr • Comments: 4

Comments: 4

19 Jan, '22
es
+1 Git lfs file locking is mature enough that this would be a valuable feature. We use git lfs locking to manage our binary resources
02 Dec, '22
Sean
I would have purchased GitKracken today if it had graphical support for LFS locking.
I have a team working with access databases, and LFS locking is a great solution.
1
11 Oct, '23
Adam
I'm going to hopefully bump this back into view for the GitKraken team.

Comprehensive LFS lock support would be a game changing feature for a client like GitKraken. One of the major drawbacks of git in general is poor binary control. The game industry lives on Perforce, SVN, and a few others in large part for this reason. It is often an exercise in futility attempting to adopt git and even if successful creates additional headaches down the road.

Obviously I cannot guarantee an industry-wide shift overnight. However, what I can tell you is that having the ability to properly juggle assets in git would create a colossal splash. There is the potential here to set precedents in workflow/usage that simply don't exist because these use cases have been ignored.

Hopefully this is encouraging. If pursued please consult with tech leaders and especially art leads in the game industry.
2
11 Apr
tolstenko
Game developer here, this feature would help our process a lot.