Request: lock per branch option instead of global lock

[aschmalt]

Writing a request for enhancement for tracking purposes to see if there is an ETA on when/if locking file per branch vs global configuration option might be made available.

This is a needed feature for our development process to allow users to work on branches that are purposely diverged from the trunk/master. I can see where a global lock for other development processes would be helpful, but having a branch vs global locking style configuration would be extremely helpful.

This was referenced in the closed issue: #3284 and also #3365

[bk2204]

Hey, thanks for writing in.

I agree this would be a nice feature to have. We don't currently have a plan to implement this at the moment, but we'll keep track of it. Part of the difficulty in implementing this is that a server will have to also recognize that a request is not global and provide the correct locking semantics.

[nintenjo64]

I am also interested in this feature support. As a game developer we deal with a lot of binary assets that dont merge so relies on Locking files to prevent clashing.

[S1M0N]

My team would also be interested in this functionality. Perhaps as an option flag in .gitattributes per file type that we want locking enabled on as well, this would allow flexibility where the default is global locking, but with the proper flag you can specify that some files or file types are branch only locking. This would resolve some workflow issues we have encountered when working within branches.

[nintenjo64]

As I understand it branch locking is impossible right now as that’s not how LFS works, which is its major downfall. Global locks are the only form of lock support per file type.

…

Sent from my iPhone

On 19 Jul 2019, at 22:37, Simon Roth ***@***.***> wrote: My team would also be interested in this functionality. Perhaps as an option flag in .gitattributes per file type that we want locking enabled on as well, this would allow flexibility where the default is global locking, but with the proper flag you can specify that some files or file types are branch only locking. This would resolve some workflow issues we have encountered when working within branches. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

[bk2204]

This requires both server- and client-side support, so while we could implement it within the client, it wouldn't be effective unless the server supported it as well. We'd also need to find a way to make the server side reject requests that were for branch locking if it didn't support them.

So while we're tracking this as a thing to have, and we'd be happy to see proposals if folks are interested in coming up with a solution, it's not an entirely trivial thing to implement.

[adrian-j-programmer]

I wish this was implemented as well... Without this feature branching workflow with git LFS has very limited application for projects that use feature/stabilization and hotfix branches.

[douglaslassance]

As I also really needed this, I started working on my own solution. Maybe you'll find it of interest.

[grzpotry]

+1