Added git config lfs.locksverify false to quickstart #115
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Member
Author
|
@anuveyatsu @shubham-mahajan can you guys check this? Thanks, |
Member
Author
|
Issue that this PR fixes: #110 |
Member
|
LGTM @anuveyatsu Could you please check once from your end. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When going through Getting started document there is an 405 error that occurs while accessing locks/verify method on LFS.
Now when I added lfs.locksverify configuration that is skipped for whole repo and it's working fine.
Also when calling the command: git lfs track "*.bin" it changes the newly created '.bin' file so I moved code for creating dummy file after git lfs track method.