CODEWITHSUNDEEP
gitgit-lfs
twinlakes
twinlakes

Reputation: 10258

Locking support detected on remote "origin"

I started tracking some files with git-lfs. Upon my next git push, I get constant (censored) message:

Locking support detected on remote "origin". Consider enabling it with:
  $ git config lfs.<repo_url>.git/info/lfs.locksverify true

When I run git config lfs.<repo_url>.git/info/lfs.locksverify true, the command exits with success and no output, and the same message continues to print with every git push.

Considering we have automation scripted around git output, how can I disable this message? Will every git client using my repo now have to run the same remediation?

Upvotes: 7

Views: 10496

Answers (1)

Jijo John
Jijo John

Reputation: 1674

When you run $ git config lfs.<repo_url>.git/info/lfs.locksverify true, it added to your git workspace/local config file. when your re-clone the workspace, it is not present.

You can verify that by running $ git config --list

To avoid asking this every time, add that your global/system (--global) git config in the build machines.

$ git config lfs.<repo_url>.git/info/lfs.locksverify true --global

Upvotes: 1

Related Questions