They should simply pull and checkout the new state of the world, their repository will work as-expected without Git LFS installed. gitattributes telling Git to invoke Git LFS when you re-run git add, so your files are added as expected.Īnother caveat of this case is that you must have a local cache of all Git LFS objects for this to work, which you can accomplish by git lfs pull -all. Even though Git LFS is configured in $HOME/.gitconfig, your repository doesn't have a. This could occur before step (2) and instead of step(1), which would leave Git LFS installed on your system (in the case that you might interact with a repository that is using it in the future) but would make step (2) do what you expect. I think that the ultimate solution to this is a git lfs migrate export command.Īs you noted, this does not rewrite history, so checking out previous revisions of your repository under Git LFS will check out pointers, not large objects. In one sense, I'm glad that we have this issue open in order to point people in the right direction should they want to uninstall Git LFS, but in another sense I think that this 5 (6?) step process is too complicated, and should be handled by Git LFS.Īnother confusing aspect of this is that git lfs uninstall can be misleading in that it leads users to think that it is "uninstalling" Git LFS from your repository, when it is really uninstall Git LFS from your system. I agree with the steps you outlined above, and left a few specific thoughts below. Oh, and obviously, i need some help with the points ending in lots of question marks - once we work through this, i'd like to edit this post into a nice clean list of steps that people can follow - then maybe let's formalize this into some documentation i just want to move forward with my collaborators once this is taken care of I'm guessing they just need to git lfs uninstall?ĭo they also need to git lfs untrack stored files or anything like that?Īlso, i have no interest in rewriting git history here, that's silly. What do we tell our fellow contributors to do? Maybe once i figure out step 2, this'll be done I'm guessing we git lfs untrack them one-at-a-timeĮdit: nope, untrack doesn't remove them. How do we remove remaining files, seen via git lfs ls-files? This will apparently prevent lfs from resurrecting itself git add myfile.psd - add the "normal" file. git rm -cached myfile.psd - "remove" the lfs file.ok, ok, i know that line never works in any relationship )Įdit: ok, there's some talk in this issue about a methodology Is there a way that git lfs can do this for me? after all, it was the one who created this mess to begin with. gitattributes stepīut how the heck do we do this? (sure don't want to accidentally change all my newlines, hah) Good thing i read just now that this must be done before the. The only caviate is you don't want to reset the. I'll have to test this some, but this might get you in the right direction. This is the same procedure in how you change the auto newlines in a git repo. gitattributes and trigger the git index that every lfs file is different, and then add and commit those files. You can probably remove the entries from. How can we reindex/re-commit lfs'd files to restore them? This removes hooks and smudge/clean filter configurationĪnd this is only the beginning, mua-ha-ha it's github pages! (github pages doesn't support lfs) So let's make this easy together - and remember - its not you, it's me I was delighted when git lfs was so easy to install and get started with - but it starts to feel frustrating when git lfs is difficult and confusing to break up with - and boy am i confused It's time to settle this topic once and for all, because answers raised in previous issues about this have proven insufficiently formulated, or are simply outdated with deprecated commands ( #316, #641, #910)
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |