git lfs status) should I use, and what output should I look for before I attempt to commit/push? Most of the time it's just showing me blank output.Įssentially the question is: If I configured git lfs correctly, what tool (e.g. When I attempt to use git lfs ls-files I'm not sure if I need to run it after git adding the files, after committing them, or after pushing them. If it helps, the output for these files always had something like (Git: edee1ad) after each file name. However, after attempting to push to, I realized that it was clearly not the case. For example, when I ran git lfs status, it showed me a ton of files under Git LFS objects to be committed, making me think they would be added to Git LFS. It's not clear which one I should be using and what output I should be looking for. I see two related commands that might help: git lfs status and git lfs ls-files. This'll allow me to iterate and try new things. Sure, I'd love to know the proper format, but more importantly, before I attempt to push my changes to github, I'd like to verify that the match and files do indeed work correctly. I tried both and they didn't use git lfs for storage. This answer says the proper format is git lfs track "MyProject/Frameworks/**", but Atlassian's help document says I should use git lfs track "MyProject/Frameworks/". I'm not sure what the proper format for matching all files and folders recursively under the Frameworks folder is. I'm trying to add everything under MyProject/Frameworks/ to git-lfs (large file storage).
0 Comments
Leave a Reply. |