File Locking Issue - Locking One Directory Prevents Another from Being Locked

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

Description:

When trying to lock separate sibling directories in our GitLab repository, we've encountered an unexpected behaviour. After one user locks the directory, another user is unable to lock another directory and receives an error message indicating that the directory cannot be locked.

Steps to Reproduce:

• Create two directories in a project - Example: frontend, backend.
• User A locks the frontend directory.
• User B attempts to lock the backend directory.
• User B receives an error message: "This directory cannot be locked while User A has a lock on "frontend". Unlock this in order to proceed"

Expected Behaviour:

User B should be able to lock the backend directory irrespective of the lock status of the frontend directory, as they are sibling directories and not nested.