Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Error in newest beta build: The filter.lfs.clean attribute should be "git-lfs clean -- %f"
See original GitHub issueDescription
My Github desktop beta just updated to the latest release, and I’m now getting this error on launch:
The filter.lfs.clean attribute should be “git-lfs clean – %f” but is “git lfs clean %f”
Run git lfs install --force to reset git config.
Version
GitHub Desktop version: 0.8.1
OS version: macOS 10.13 Beta (17A360a)
I also use homebrew and have git 2.14.1 installed via brew.
Issue Analytics
- State:
- Created 6 years ago
- Comments:14 (9 by maintainers)
Top Results From Across the Web
What is a problem with Git and LFS in my case? - Stack Overflow
There is a git repo and I cloned it locally. Then I open Visual Studio and open my project. When I try to...
Read more >Git Large File Storage (LFS) - GitLab Docs
Read the documentation on how to migrate an existing Git repository with Git LFS. Removing objects from LFS. To remove objects from LFS:...
Read more >What is git LFS?
This filter configuration lives in your git config (e.g. at ~/.gitconfig ) and applies to all your repos. [filter "lfs"] clean = git-lfs...
Read more >342372 – support gitattributes - Bugs - Eclipse
we started working on JGit support for clean/smudge filters as a first step to support Github's LFS extension which allows to store large...
Read more >git-lfs-clean - Git clean filter that converts large files to pointers
Clean is typically run by Git´s clean filter, configured by the repository´s Git attributes. Clean is not part of the user-facing Git plumbing...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Yeah, so I think we wanna detect this case and ask the user if we should use
--forceor leave it alone.@mayel you can remove it - Desktop should install itself again on next launch and make that error go away