gh-gei icon indicating copy to clipboard operation
gh-gei copied to clipboard

Add LFS support to `generate-script`

Open dylan-smith opened this issue 3 years ago • 2 comments

We might be able to do something pretty quick to add some basic LFS support to the generated migration script (without requiring any backend changes).

What if we add a --lfs option that adds something to the script for each repo, that post-migration does something like:

git lfs fetch --all
git lfs push --all NEW-REMOTE

dylan-smith avatar Jun 09 '22 20:06 dylan-smith

would this handle the case where you have your repo in AzDO which has no upper file size limit (and as far as I can tell no LFS setup) to move to GH, which has a 100mb upper file size limit and therefore requires LFS for these larger files?

Alex-ley-scrub avatar Jul 12 '23 10:07 Alex-ley-scrub

would this handle the case where you have your repo in AzDO which has no upper file size limit (and as far as I can tell no LFS setup) to move to GH, which has a 100mb upper file size limit and therefore requires LFS for these larger files?

👋🏻 The basic change suggested here wouldn't - it'd require a deeper LFS support.

What's being proposed here is to automatically push LFS objects to GitHub which are already committed to Git LFS.

If you have large files in your Git repo that aren't yet in LFS, you'd have to move them to LFS first to benefit from this change - which would require you to rewrite your Git history, likely interrupting the migration of your pull requests.

If you have large files between 100MB and 400MB, we do have an option we can enable to allow those files to be migrated. If it's not too late, you can email me at the address on my profile.

timrogers avatar Jul 25 '23 17:07 timrogers