I'm experimenting with the File Lock mechanism, and it's unclear to me whether if the edition of locks between the CLI and Gitlab UI is supposed to be bidirectional or not.
By default, unlocked files are readonly. This matches what ls -la tells me
drwxr-xr-x 1 200207121 1049089 0 Sep 13 13:49 .git/
-rw-r--r-- 1 200207121 1049089 2738 Sep 13 13:02 .gitattributes
-r--r--r-- 1 200207121 1049089 90299 Sep 13 13:26 My_locked_file.docx
-rw-r--r-- 1 200207121 1049089 1118 Sep 13 13:02 README.md
Let's say I lock a file through the CLI. The Gitlab UI will show the file has been locked properly, and the permission for the file is locally set to read/write.
drwxr-xr-x 1 200207121 1049089 0 Sep 13 13:26 ./
drwxr-xr-x 1 200207121 1049089 0 Sep 13 13:02 ../
drwxr-xr-x 1 200207121 1049089 0 Sep 13 13:49 .git/
-rw-r--r-- 1 200207121 1049089 2738 Sep 13 13:02 .gitattributes
-rw-r--r-- 1 200207121 1049089 90299 Sep 13 13:26 My_locked_file.docx
-rw-r--r-- 1 200207121 1049089 1118 Sep 13 13:02 README.md
However, if I unlock it from the Gitlab UI, it's not unlocked on my local CLI. And I'm unsure if this is the intended behaviour or not.
Even with git checkout . or git pull , I can't figure out how to 'locally refresh' the locks, to specify it has been released. The lock remains closed locally no matter what.