Add option to disable file locking for GitLab instance
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
File locking can be a useful feature, but it can introduce it's own problems by blocking people changing files. Some customers would rather just turn it off to avoid this problem. If anyone with developer access is able to lock a file or directory this could block other people's work. Waiting for someone with master permissions to remove the lock isn't scalable.
We should provide the ability for organizations to limit file locking to prevent this problem.
Proposal
Add an option to the admin interface to disable file locking for the entire instance, including GitLab file locking and Git LFS locking.
File locking should continue to be enabled by default for new and existing installations.
Design
| Admin Area → Settings → Repository |
|---|
 |