Initializing Keybase... done. Syncing with Keybase... done. Git LFS: (0 of [redacted] files) 0 B / [redacted]B batch request: missing protocol: "keybase://private/graingert/[redacted].git/info/lfs" error: failed to push some refs to 'keybase://private/graingert/[redacted]'
~/.dotfiles/git/hooks. This path is familiar, it is the path I have on my main git config for global hooks, but I don't understand why it keeps getting created every time inside my repo. If LFS creates these hooks I think the"normal" behaviour would be place them inside the
.gitfolder. How I can go around this? Is it a configuration issue I have or something with LFS?
git lfs installin any folder installs some needed settings to global gitconfig file. In addition to that repository needs to have git hooks for post-checkout, post-commit, post-merge and pre-push? And these are usually installed automatically while performing LFS operations on the repository? But if my repository already has custom hooks, i need to manually install these there? Or is some part of the setup obsolete/incorrect?
BalinI need to migrate data from one institutional git provider to another. My repos include lfs'ed files. Does a
git clone <PROJECT_URL> && cd <PROJECT_DIR> && git lfs install --local && git lfs pullworkflow prior to changing the origin remote and pushing again retrieve ALL lfs history or just the current versions?
origin, just add new remote
git lfs push --all newremoteas per https://github.com/git-lfs/git-lfs/issues/516#issuecomment-140002103
originin local repo(s)
BalinMateusz Łoskot (Gitter): Terrific. Thank you so much for your help ... got hit by the fact that the importer of the new institutional product migrates the
lfsstubs, but not the underlying data, while happily recognizing the stub and telling you the file is
lfsed ... with a non-exisiting pointer ... LOVELY.
Balin1) git clone GITHUB_REPO
BalinReads about right?