Running the command gives:Įlapsed Time for timer 'Default': 0:00:00.42Įlapsed Time for timer 'Default': 0:00:00.34Įlapsed Time for timer 'Default': 0:00:00.40 (People want to lock their MS Word '.docx' files.) Our 'Documentation' repo is where we're intending to use the locking. This was our largest repository (>40,000 files), but so far it has no Lfs ls-files' in a Windows bat file, then running it three times gives meĮlapsed Time for timer 'Default': 0:00:06.50Įlapsed Time for timer 'Default': 0:00:06.52Įlapsed Time for timer 'Default': 0:00:06.42 I don't have this git repo under linux, but wrapping a timer around 'git We looked for other Git GUIs to see if anybody did this well, and in the short time we spent looking, we didn't find any. That's the approach I would take, if I were coding it. Perhaps with a warning if more than X files are being locked/unlocked at a time. Being able to select a directory for lock/unlock (so the 'lock/unlock' happens on all the files contained in that directory, recursively) is helpful.Selecting files, then right-click context menu to lock/unlock is good.

Showing the name of who has a file locked is incredibly helpful.I find the current ways to access the file tree in Fork to be awkward.Being able to paste a directory name or filename, to jump to that location in the file tree would be used frequently.Also, a way to show a list of just the locked files is very important.Having to start navigating at the root every time is painful. Being able to return to the directory view they were at when they closed the app is good.It answers the question: 'what is locked, what is not locked?' Easy access to a file tree is huge, because it becomes that (non-tech) person's primary interface.Some of our users are somewhat non-technical (I mentioned.As former Perforce users, we're familiar with how smoothly this can work. The obvious choice for shared binary file editing is locking the files.docx, but also more complex multi-data-file applications). We have several non-programmers who have needs for shared binary file editing (primarily.

Programmers are fine with vanilla Git - it works well for code, obviously.

Our small company has chosen Fork because we programmers were making the decision. Like I also come from a Perforce / Game-Dev background, and have only been using Git for about a year, in a different industry. I'm glad others are showing interest in file locking! If there's more git-o-logic ways to do this, I'm very curious though.Īnd yes, for that point of view, seeing a list of locked files would be a great feature as well, either as its' own tab, or as a filter in File-Tree view.Īlso, it would be great to be able to quickly see all locks from a user/me, as well as all locks set on a project by everyone (hence a File-Locks tab would make sense). So spending 2 seconds to set a lock is a small price to pay, opposed to throwing away weeks of work :D ). and the time frame needed to work on a binary file could be multiple days to weeks. people from Perforce etc are very much used to having to traverse the file tree regularly anyway. So in that context, git-fork would mostly act as an overview / VCS management tool, and showing locked files (via an icon/marker) in File-Tree only is pretty standard as well as navigating the TreeView to lock a file is generally not considered 'too long' for people used to that world (i.e. Unreal/Unity Editor/Plugins themselves and passed onto the VCS (and usually before, or at the point of the very first edit of said file - which is when conflicts would appear when attempting to set the lock - and it's mostly about communicating the fact that another user is working with the file for the VCS). I come from a Game-Dev / Perforce background, and would like to use git/bitbucket/etc as an alternative for such (so take my input with a grain of salt as I am still learning the git ways.).Īlso, this is a requirement for collaborative team projects mostly and when a lot of binary files come into play.Īs for the questions (from my perspective):įile Tree tab & file context menu in the TreeView would be the most likely entry point in Git-Fork for me.Īs for your worries - in Game-Dev, a File-Lock itself will often be issued from another tool anyway i.e.

Lock track changes in word