Sign in or sign up before continuing. Don't have an account yet? Register now to get started.
Make LFS file locking use the same DB table than File Locking feature
<!--IssueSummary start-->
<details>
<summary>
Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards.
</summary>
- [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=6194)
</details>
<!--IssueSummary end-->
Right now we use separate tables for LFS file locking and the File Locking feature.
Given these features are very similar with the main difference that File Locking has a UI to lock/unlock a file we should consider using a single table in order to avoid some DB complexity and also try to reuse some code.
This change should consider two important things:
1. Migrate the data from the LFS file locking table to the table used by File Locking.
1. Backport to CE the necessary changes.
issue