### Problem to solve The existing [Default branch file and directory locks](https://docs.gitlab.com/ee/user/project/file_lock.html#default-branch-file-and-directory-locks) is only available via the application GUI, making it hard to automate this step as part of a release process. ### Further info Currently, users can register a file type as lockable with LFS and use a remote server that implements LFS file locking API. Both of these options should be available in GitLab. ### Proposal In the larger effort to [extend file locking options](https://gitlab.com/groups/gitlab-org/-/epics/5884), we should implement an API endpoint for each lock operations. This particular one would the existing functionality offered in-app. ### Links