You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
How can I use the same lfs test server to test the locks of different repos?
I want to store the locks of 2 different repos on the same server but have sth to differentiate between locks of the same path in different repos.
Suppose I have repo1 and repo2. and there is some file that has the same path on both repos. let's say it is "NewFolder/f1.txt". If I run git lfs lock "NewFolder/f1.txt" on repo1 Then run the same command on repo2. I don't want the command to fail because of lock already exists.
The text was updated successfully, but these errors were encountered:
From what I can see in the code, locks should be stored per-repository. That's definitely the intended behaviour from the client perspective, and I believe it's the behaviour that should be occurring in the test server. Therefore, I don't expect the locks to conflict.
Are you seeing something different, or are you just asking to verify?
Hello,
How can I use the same lfs test server to test the locks of different repos?
I want to store the locks of 2 different repos on the same server but have sth to differentiate between locks of the same path in different repos.
Suppose I have repo1 and repo2. and there is some file that has the same path on both repos. let's say it is "NewFolder/f1.txt". If I run git lfs lock "NewFolder/f1.txt" on repo1 Then run the same command on repo2. I don't want the command to fail because of lock already exists.
The text was updated successfully, but these errors were encountered: