Add support for Git LFS 2.0.0 File locking mechanism

Sébastien Rombauts 7 years ago updated by Marc Strapetz 7 years ago 5

Newly released Git LFS 2.0.0 comme with centralized "File locking".

  • For now it is only supported by Github.com, but I expect Gitlab and Bitbucket to follow sooner or latter.
  • It is only working with a centralized repository, that is when sharing a repository in a Github Organization, or when using a dedicated "on premise" server (using Gitlab there).

  1. It would be great to add support for the new "git lfs lock", "git lfs unlock" and "git lfs locks" commands.
  2. This would require at least a new status icon (Lock) but probably two (Lock by other), a row with the name of the user locking the file,

Note that in my experience, the command line is currently a bit confusing (HTTPS seems to work reliably only when basic authentication got through an explicit https://username@gitlhub.com URL).

Wouldn't it make sense to comment at http://smartgit.userecho.com/topics/65-gui-for-git-lfs/ instead of adding this as new RFE? This way, votes will be concentrated at a single Git-LFS issue.

I can do that (I will do), but please bear in mind that this go beyond the simple "Git LFS 1.x"

I understand. It's reasonable to support Git LFS 2 commands from the beginning (not just Git LFS 1).